The purpose of WOLongResponsePage is to stop your session from timing
out, and to allow users to view progress and cancel an operation. It
shouldn't block other requests assuming you have multiple workers
running... unless of course you're locking some resource during the
long response page.
On Nov 17, 2008, at 4:24 PM, David Avendasora wrote:
Hi all,
I am trying to make use of WOLongResponsePage for a long-running
process (5-10 minutes). I thought that part of it's job was to allow
other requests to be responded to while it runs. It seems to still
be blocking other requests until it finishes. Am I missing something
fundamental?
Dave
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/kenlists%40anderhome.com
This email sent to [EMAIL PROTECTED]
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
