Hi Andy,
>> Connection pooling has to be managed by you in some form or other. If
you are using a middle db connector such as dbAnywhere from Symantec then
connection pooling is dealt with by it, otherwise you would need to
implement a thread safe connection pool class or classes.
Pooling connections at the servlet is not influenced by any other forms of
connection pooling implemented else where. All you are doing is using 2
pools, one under your own control and the other transparently.
In otherwords, there is are restriction placed on you other than the
maximum number of connections that you can have to your database server,
regardless of how you do things. <<
This means you don't know of any database (including Access) that would not
allow for using connection pooling. Is that correct?
Upon further thinking about it, I found that it may not be totally
impossible for a database to impose restrictions. For example, a database
might request that all operations (open - yielding a handle, do something -
using the handle, close - using the handle) must be executed by the same
thread. Such a database would only allow for one user at a time. Is that
only a theoretical possiblity or do databases of this kind really exist?
Regards,
Heinz Wehner
(Karlsruhe, Germany)
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
