Thank you for the gentle reminder; I'd spaced the part about
multi-user.
could an alternate method might be this:
When the first browser request hits the server, the servlet
spawns two, related processes. The two processes "know" each
other and can communicate. The two processes each receive
the appropriate request / response pair, and the servlet
response causes the browser to "spawn" a new window, showing
the second frame. Then, changes in the second "frame" can
use the session ID to contact the second servlet, which knows
the first servlet, and the first servlet is periodically
contacted--via its session ID? That way they track
themselves. Each new user gets a different session ID and
servlet pair?
On Tuesday, August 24, 1999 7:32 AM, Ashok Kumar
[SMTP:[EMAIL PROTECTED]] wrote:
> Greg,
> Thanks for your response. I tried the similar thing.
> But the question
> is where to keep the parameters in the servlet. Specialy in
> the multi-user
> environment how will the client Applet know for which
client
> this request
> or parameters are set. Also Multiple clients can overwrite
> the parameters at
> the same time. So I need to make them thread safe.
> I tried to use the HTTPSession to set the parameters. In
> this case I didn't
> use two servlets as u suggested, one dedicated to serve F1
> but I used the
> single Servlet. HTML from F2 sets the parameters in
> HTPPSession in Servlet.
> Applet in F1 keeps polling on the Servlet HTTPSession and
as
> soon as the
> parameters are set it reads them and sets them back to
null.
>
>
___________________________________________________________________________
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
