Re: When (not) to use session().defaultEditingContext()
Re: When (not) to use session().defaultEditingContext()
- Subject: Re: When (not) to use session().defaultEditingContext()
- From: Geoff Hopson <email@hidden>
- Date: Fri, 29 Oct 2004 20:01:38 +0100
I'm not so sure that's a good thing to do. I recall that if you ask an
EO for it's editing context, a general message is sent out to the object
store coordinator saying "Does any one of the editing contexts under
your control have me as an object instance in their object graph?". The
object store coordinator then messages each of the ECs it knows about,
asking if they hold the specified instance.
If you have a system with 1000s of sessions/editing contexts, that's a
lot of messages.
It may have changed in more recent versions of WO. And if you have a low
usage system, you probably won't notice.
I'm sure the gurus will step in and correct me.
Geoff
On Fri, 2004-10-29 at 19:26, James Cicenia wrote:
> My two cents..
>
> the whole editing context thing was very confusing to me until I
> realized that I could get the current
> editing context of the object I am editing. This made it really easy
> for me to understand.
>
> Also, I use a lot of popup windows which allows me to transactionalize
> those processes separately
> and of course within their own editing context. I used ... I think it
> was Jonathon Flemmings code to
> handle locking and unlocking of the editing contexts.
>
> -James Cicenia
>
> _______________________________________________
> 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
_______________________________________________
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