I'm about to prototype a Servlet implementation that has to make use of an
'API'-like class to handle client requests. This API class sets up a socket
(well, 2 actually: one client socket that sends requests to a legacy system
on a different host, and one listener socket that listens for async
notifications from the other host). I need to persist these socket
connections in my Servlet's HttpSession so that my client can login once,
and post more requests during this session that'll go out over the socket to
the other system (the other host will send the response back synchronously
over this same socket, and my servet will format the response data into html
for the client browser).

I've looked around for info on what types of objects are 'ok' to persist in
the session and what types are definite no-nos, and couldn't find any info
pro or con if persisting UNIX resources like sockets (connect and listen)in
the session is even possible.

really appreciate any help on this...
Paula Young

___________________________________________________________________________
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

Reply via email to