• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Project Wonder: SharedEditingContexts
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Project Wonder: SharedEditingContexts


  • Subject: Re: Project Wonder: SharedEditingContexts
  • From: Lachlan Deck <email@hidden>
  • Date: Mon, 15 Sep 2008 17:13:25 +1000

On 15/09/2008, at 2:08 PM, Mike Schrag wrote:

Does Project Wonder also have a replacement for EOSharedEditingContext??
Project Wonder's replacement is "don't use it" ... So no.
Err .. no -- come on, be fair -- this is not true. It's just that most people don't use it == scared of it == don't use it because of misinformation.
It is the case that neither Anjo nor I recommend it or use it, which is why I say this.

Fair enough. You can't recommend something you don't use. I'm just commenting that this doesn't necessarily need to mean 'bad stuff will result if used'...which is usually the tone given for the sec... but rather, from your point of view, 'unknown stuff will happen if used'. That's all I was saying. It does appear to me that the sec receives unnecessarily bad press.


Many people use SEC incorrectly (just skim the archives), it's easy to accidentally do so,
and the result of this is often a deadlock.

Well - it appears to me that many people don't use it to begin with for this to be true ;-)
But seriously, it's been a while since I've seen any such problems on the list.


We make a lot of different types of apps, and I have not found a case where I feel that leaving out SEC has really hindered me.

Sure. Dov appears to be using it quite a bit... and I'm simply (attempting) to point out that the move to Wonder doesn't necessitate refactoring to work.


So the following properties is what I have
er.extensions.ERXApplication.defaultRequestHandlerKey=wa
er.extensions.ERXApplication.useEditingContextUnlocker=true
er.extensions.ERXEC.defaultAutomaticLockUnlock=true
er.extensions.ERXEC.useSharedEditingContext=false
er.extensions.ERXEC.defaultCoalesceAutoLocks=true

Then using the shared ec as documented is no probs. I've not tested having the following property as true - but I believe it should be fine also.
er.extensions.ERXEC.useSharedEditingContext=true


So sure, as with anything, if you understand it and know that you're using it properly, more power to you. I personally don't think it's worth it.

Again, if you're happy with what you have - great. I suspect that Dov was happy with what he had too and with the introduction of JGroups syncrhonising the move to Wonder has brought about these questions.


You happen to be someone who puts in the time and effort to properly use some of the more esoteric features of EOF, which is great, but lots of people aren't willing to do that, which is a great way to accidentally trip yourself up.

Sure.

with regards,
--

Lachlan Deck
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


References: 
 >Re: Project Wonder: SharedEditingContexts (From: Dov Rosenberg <email@hidden>)
 >Re: Project Wonder: SharedEditingContexts (From: Lachlan Deck <email@hidden>)
 >Re: Project Wonder: SharedEditingContexts (From: Mike Schrag <email@hidden>)

  • Prev by Date: Re: Re: WebObjects Installer CD for Windows
  • Next by Date: Re: Re: WebObjects Installer CD for Windows
  • Previous by thread: Re: Project Wonder: SharedEditingContexts
  • Next by thread: ERXEC.newEditingContext() instead of the defaultEditingContext()
  • Index(es):
    • Date
    • Thread