Hi all, There have been a number of threads discussing this runtime option. I think the consensus opinion was that although it is off by default, it is better switched on.
Presumably there are some basic additional rules to follow. For instance, AFAIK components will not be shared by multiple threads as they will be instantiated as one goes along or will be returned from the page cache as part of a single session - and as one session will be handled by only one thread, this is fine. How does concurrent handling interact with stateful and stateless components? Perhaps more of an issue is that code within my EOF classes may be executed by more than one thread at a time. I use lazy initialisation but there is a race condition there. Fortunately, most of the time there are no side-effects and running that code twice would have no significant deleterious effect. For situations where it would matter I would assume protecting lazy initialisation with a double check and a synchronised block for the inner check would be fine? Is that interpretation correct? Are there other commandments? -- Dr. Mark Wardle Specialist registrar, Neurology (Sent from my mobile) _______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
