Re: When (not) to use session().defaultEditingContext()
Re: When (not) to use session().defaultEditingContext()
- Subject: Re: When (not) to use session().defaultEditingContext()
- From: Ben Ketteridge <email@hidden>
- Date: Fri, 29 Oct 2004 12:25:45 +0100
On Fri, 29 Oct 2004 13:18:02 +0200, email@hidden
<email@hidden> wrote:
> P.S. Of course every application has its own needs. An editing context use
> strategy should be defined with those needs in mind.
That was the point I was trying to make in the first place :)
Our app is actually considerably more complex in it's use of
Session-based objects than I described above, so your solution doesn't
suit our requirements. I was just trying to illustrate how a strategy
like creating an editingContext for every transaction won't
neccessarily suit everyone - as you point out above.
Ben.
--
| Ben Ketteridge email@hidden, aka Gremlin |
| It is by caffeine alone that I set my mind in motion. |
| It is by the coffee that the thoughts acquire speed, |
| the lips acquire stains, the stains become a warning. |
| It is by caffeine alone that I set my mind in motion. |
_______________________________________________
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