Even with concurrent request handling turned on, access to the database is serialized.

Two backdoor ways of getting an additional EOF stack:

Most long queries (after optimization) I've had were related to reporting. Moving the reporting to a separate application prevented the long query from interfering with more typical user access (and educated users' expectations).

If the application is for use by a limited number of users, e.g., internal customers, increasing the number of instances may reduce the likelihood of other users waiting.

        Tom


On May 4, 2010, at 3:17 PM, Ricardo J. Parada wrote:



If I have concurrent request handling enabled and I have a query taking a long time, will other requests block when they try to access the database until the request that issued the long query finishes?

Thanks,
Ricardo


 _______________________________________________
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/blenko% 40martingalesystems.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]

Reply via email to