Hi Chuck
As always, thank you for your answer.
I've been experimenting with the long response page.
curiously, part of my long response is a rather lengthy fetch,
followed by lots of delete's, inserts, etc.
even when i kick this off in another thread the app thread blocks
during save changes, even though no database requests are happening
in the app thread.
does this sound like something you've encountered before?
many regards and thanks
Cornelius
On 04.09.2007, at 17:59, Chuck Hill wrote:
Hi All
I see that my app answers the following request:
/cgi-bin/WebObjects/SFDev.woa/womp/instanceRequest
The strange thing is, when my app is really busy handling, you
know, stuff. the instance request doesn't get answered. The app is
alive and well, just really busy.
Is there a way to get the instance requests to work in a
multithreaded manner?
I could be wrong, but I thought that these were handled in a
different manner that does not wait for regular, session based,
requests to be served.
So that the app can handle long requests, or do i have to use
AjaxLongResponse, or some such, to let the main app handle the
instance request?
ConcurrentRequestHandling enabled is on, I guess that's more for
concurrent session requests?
If that is on, then something else is going on. I suspect that as
your long request runs, other non-womp requests build up behind it
and that is what makes wotaskd think there are problems. A long
response page is probably the right answer here, unless you can
optimize the page to make it quick.
Chuck
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-deploy mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-deploy/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
