Lists

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

Re: default editing context locking in directaction

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

Re: default editing context locking in directaction

Subject: Re: default editing context locking in directaction
From: Robert Walker <email@hidden>
Date: Wed, 20 Jul 2005 09:17:39 -0400

I generally avoid using the session's default editing context within direct actions. A call to session().defaultEditingContext() will create a session, even if you don't actually need one. It can be more efficient to use a new editing context and lock it as necessary, since this will not cause unnecessary sessions to be created.

On Jul 20, 2005, at 2:50 AM, Mike Schrag wrote:

If i call session().defaultEditingContext() from within a DirectAction, I'm currently defensively locking it. Do I need to, or does it follow the same (automatic) locking rules as in a normal WOComponent?

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


_______________________________________________
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:  
  >default editing context locking in directaction (From: Mike Schrag <email@hidden>)




Prev by Date:
Re: default editing context locking in directaction

Next by Date:
Workaround: Using EOModels with xCode 2.1 without EOModel beeing	corrupted

Previous by thread:
Re: default editing context locking in directaction

Next by thread:
Workaround: Using EOModels with xCode 2.1 without EOModel beeing	corrupted

Index(es):

Date
Thread