Re: Writing a custom request handler
Re: Writing a custom request handler
- Subject: Re: Writing a custom request handler
- From: Hsu <email@hidden>
- Date: Wed, 6 Aug 2003 00:38:20 -0700
Custom request handlers don't participate in the concurrency locks of
the RR loop. If you want them to behave in a similar way, synchronize
at appropriate points against WOApplication.requestHandlingLock(). If
you don't, WO will happily invoke handleRequest() from dozens of
threads on your request handler in parallel.
Karl
On Tuesday, August 5, 2003, at 03:08 PM, Jonathan Rochkind wrote:
I'm writing a custom request handler. What can I assume about
concurrent access to my WORequestHandler object? Will the framework
instantiate a new object for every request? Can I safely store
request-specific data in iVars in my WORequestHandler object for the
duration of request handling, and not be concerned that WO is going to
try and concurrently access my WORequestHandler for some other
request? When I'm done handling the request, do I need to reset all
iVars, because the framework might then use the very same object for
another request? Or what?
Any advice on custom request handlers in general?
--Jonathan
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.
--
pthbbbbbbbbbbbt.
Homepage:
http://homepage.mac.com/khsu/index.html
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.