yes, that is what we did also. Seissions and contexts has got some
sence if you can restore that after engine crash (some like EJB :)
Otherwise you can do all that stuff by your own and at least be free
from implementation bugs (lost sessions, duplicate sessions etc).
>Dmitri:
>No reason I can think of. I use a single connection pool singleton object
>for both servlets & server-side java objects, works great.
>Mike N
>Javacorporate Ltd
ColdJava: java server side programming
http://coldjava.hypermart.net
____________________________________________________________________
Get your own FREE, personal Netscape WebMail account today at
http://webmail.netscape.com.
___________________________________________________________________________
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
