concurrent request handling: advice
concurrent request handling: advice
- Subject: concurrent request handling: advice
- From: Jonathan Rochkind <email@hidden>
- Date: Tue, 6 Jan 2004 14:38:08 -0600
So, I have a large set of applications and frameworks that have grown
over a few years to have many many lines of code.
I want to take the plunge and turn on concurrent request handling.
Does anyone have any advice for what things to look at in my app that
I might need to modify to be safe under this environment?
The only things I can think of now are: variable access in
Application, or in any static methods/variables. Those seem to be
the main areas I will need to make sure are safe for concurrent
access once I turn on concurrent request handling. Stuff at the
WOSession level, or in any particular WOComponent---shouldn't need to
worry about this, since access to a session is still one thread at a
time, and a component normally lives within a certain session. Same
with EO objects.
But is there anything else I should be thinking about? Advice from
someone who's written, or better yet converted into, a large
concurrent request handling WO app especially welcome.
--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.