Re: How does WO enforce serial request processing per session?
Re: How does WO enforce serial request processing per session?
- Subject: Re: How does WO enforce serial request processing per session?
- From: Chuck Hill <email@hidden>
- Date: Mon, 27 Aug 2007 09:19:59 -0700
On Aug 27, 2007, at 12:51 AM, Peter Vandoros wrote:
Hi List,
I was wondering how WebObjects enforces serial access to the
WOSession (ie. request processing).
Does the "wo" request handler enforce serial access? Does the"wa"
request handler enforce serial access? Does
Application.dispatchRequest() enforce serial access?
Also, if I was to access a WOSession outside of a request-response
loop, how can I ensure that the WOSession is not processing a
request at the same time? How can I ensure that only one Thread
accesses the WOSession at a time that comes from a "da" request?
How do I initialise the WOSession correctly if I need access to it
when not coming from a "wo" request the "wosid" is not sent along
with a "wa" request?
See WOSessionStore and related methods in WOApplication. See
Practical WebObjects pages 171 - 172,
Is WOApplication.restoreSessionWithID() going to do "the right
thing" when ever I call it? ie. is it going to initialize the
WOSession correctly? will it ensure serial access to the WOSession?
etc...
Yes.
Chuck
--
Practical WebObjects - for developers who want to increase their
overall knowledge of WebObjects or who are trying to solve specific
problems.
http://www.global-village.net/products/practical_webobjects
_______________________________________________
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