Lists

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

Re: Object Store Coordinator and User Info – Is this Dangerous?

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

Re: Object Store Coordinator and User Info – Is this Dangerous?

Subject: Re: Object Store Coordinator and User Info – Is this Dangerous?
From: Andrew Lindesay <email@hidden>
Date: Wed, 29 Oct 2008 14:01:38 +1300

Hello Chuck;

I seem to remember this point now... not using concurrent dispatch too much so the details get forgotten.

cheers.

You expect that you mean to lock the OSC? I thought that the OSC gets locked when you lock the EC?

...

No, of course not. An ec (the defaultEditingContext) gets locked each time the session is awoken. If this locked the OSC, concurrent dispatch would not be possible. The OSC only get locked while fetching or saving.


___
Andrew Lindesay
www.lindesay.co.nz

_______________________________________________
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:  
  >Object Store Coordinator and User Info – Is this Dangerous? (From: Andrew Lindesay <email@hidden>)
  >Re: Object Store Coordinator and User Info – Is this Dangerous? (From: Peter Vandoros <email@hidden>)
  >Re: Object Store Coordinator and User Info – Is this Dangerous? (From: Andrew Lindesay <email@hidden>)
  >Re: Object Store Coordinator and User Info – Is this Dangerous? (From: Chuck Hill <email@hidden>)




Prev by Date:
Re: wosid != session().sessionID()

Next by Date:
Re: Class.this.. ?

Previous by thread:
Re: Object Store Coordinator and User Info – Is this Dangerous?

Next by thread:
Re: Object Store Coordinator and User Info – Is this Dangerous?

Index(es):

Date
Thread