How does WO enforce serial request processing per session?
How does WO enforce serial request processing per session?
- Subject: How does WO enforce serial request processing per session?
- From: Peter Vandoros <email@hidden>
- Date: Mon, 27 Aug 2007 17:51:11 +1000
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?
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...
Thanks
--
Peter Vandoros
Software Engineer
Etech Group Pty Ltd
Level 3/21 Victoria St
Melbourne VIC 3000
Australia
Ph: +61 3 9639 9677
Fax: +61 3 9639 9577
----------------------------------
IMPORTANT: This e-mail message and any attachments are confidential and
may be privileged. If received in error, please reply to this message
and destroy all copies and any attachments. You should check this
message and any attachments for viruses or defects. Our liability is
limited to resupplying any affected message or attachments. For more
information about Etech Group, please visit us at
http://www.etechgroup.com.au.
_______________________________________________
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