Hi All
I just finished reading the archive for a solution to my problem, but it
seems that it is unresolved one. I would appreciate a solution or an
alternative way to solve the problem.
- I am developing a Browser Interface that act as an alternative to an
existing Java Swing application.
- The existing Java Swing application communicate with a Java server
through sockets. The java client takes all the information and data from
that Java server (the server actually acts as an interface to a legacy system)
- What I was planning to do is to develop servlets that communicate to the
current Java server as a normal Java client, i.e the Java server will think
that the browser client is actually an old java client. thus I will not
need to change the code of the Java server.
-As I mentioned, the Java server use socket for communication, after
establishing a connection, it will start a thread that will be responsible
for all the communication. if any error occur in the socket, the thread
will be cleaned up and another initialization will be required for that
client.
The problem now is how can I maintain these socket connections with
servlet, taking into consideration that I am planning to use different
servlets (one for login, another one for search...etc), so I need not only
to maintain the socket for the current servlet thread, but also across all
servlets.
I would appreciate your feedback and ideas.
Regards
Rabah
Maxim Group
___________________________________________________________________________
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
