>>> "Christopher K. St. John" <[EMAIL PROTECTED]> 01-Nov-00 2:59:36 PM
>>>
>A safer/simpler architecture might be to have a non-servlet
>service that could be started/shutdown based on requests
>handled by the servlet.
I've never had a problem with creating ServerSocket's within servlets
but Chris is right. It *could* be dangerous.
As he says a way round it would be to create a daemon thread which
created the ServerSocket.
Another way round it would be to put a reference to the ServerSocket
in the servlet container's context attributes.
BVut I think the best way would be to check whether your servlet
container does reloads in the way Chris describes. If it does... get
another one /8->
Nic Ferrier
___________________________________________________________________________
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
