Lists

Terms and Conditions
Lists hosted on this site
Email the Postmaster
Tips for posting to public mailing lists

Re: EOEditingContext Lock/Unlock best practice?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: EOEditingContext Lock/Unlock best practice?

Subject: Re: EOEditingContext Lock/Unlock best practice?
From: Guido Neitzer <email@hidden>
Date: Wed, 8 Apr 2009 11:50:24 -0700

On 8. Apr. 2009, at 10:13 , shravan kumar wrote:

How about if I use session's defaultEditingContext and where needed I will just revert the EC, if I do not need to persist the objects in the EC? Most of our app uses session's defaultEditingContext.

I think that is a pretty bad idea as you might miss point to revert it and end up with a non-working defaultEC if people use back-button or other "bad" things.

For any EOF using app, I recommend the use of Wonder or at least the MultiECLockManager (was that the right name?).

cug
_______________________________________________
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: EOEditingContext Lock/Unlock best practice? (From: shravan kumar <email@hidden>)




Prev by Date:
Re: App Engine supports Java

Next by Date:
Re: App Engine supports Java

Previous by thread:
Re: EOEditingContext Lock/Unlock best practice?

Next by thread:
Re: EOEditingContext Lock/Unlock best practice?

Index(es):

Date
Thread