WO blocking/threading question
WO blocking/threading question
- Subject: WO blocking/threading question
- From: Michael Engelhart <email@hidden>
- Date: Fri, 13 Aug 2004 11:31:28 -0500
Hello all. Sorry about all the questions from me today...
This is something that after reading all the books and docs I still
don't fully get.
If I have a site where 100 users come to the site at the same instant
and all do a search (i.e. a SELECT, not an UPDATE or INSERT or DELETE)
also at the same instant (hypothetically), does WO block while each
request is handled? It seems that in the default deployment that WO
only uses a single database connection and in the case of my JDBC
driver (postgresql), the driver is synchronized so only a single call
can be made through one JDBC connection at a time. If it doesn't
block on SELECT, does it block when doing SQL updates/deletes?
I can't really see how this can be the case since it would seem that WO
would be the worlds slowest application server unless you always had
100 or more instances running at the same time for a high volume site.
On a related note, I have queries that are non-JDBC related (legacy
data) that use pooled network connections that I control and dole out
to the user on request. Does WO block while for these types of
requests are being processed? I put these legacy queries in a
WOLongResponsePage in an effort to allow multiple users to be calling
the legacy system at the same time because according to the docs these
spawn new threads. The legacy system can take 5-10 seconds to
responsd in most cases.
My limited understanding is that at least the request/response cycle is
threaded so that if you just have a WO app that doesn't do any database
access, it will handle concurrent requests just as any other
application does.
Thanks for any insight.
Cheers
Mike
_______________________________________________
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.