> > why is storing a database connection in a session crazy? You don't
> > say why. Jason Hunter seems to think it is good enough
> > to use as an example in his book. I use it to great effect in web
> > apps.
>
> Just want to point out, the text around that example has a paragraph
> that begins, "Storing connections in sessions requires careful analysis
> of your application's needs." :-)
>
> -jh-
>
Hi Jason,
and after careful consideration of the application needs I used that method
instead of using a ConnectionPool.
One of the prime considerations was time to online and this method is simple
to implement, future
improvements to the application call for a Singleton Connection Pool for all
JSP's that need it.
In testing there are very few requests going through the server hence there
being no need for a connection pool.
As the system grows then there will be a transition from session stored
connections to a servlet based ConnectionPool
to serve the JSP's.
As I have a deadline that cannot possibly be moved I chose this as the most
suitable temporary solution :)
Andy Bailey
___________________________________________________________________________
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
