"Ibrahim, Sultan (IndSys,MKT)" wrote:
> That depends on which server u are using. If u are using the application
> server, that in turn process the request at different server, then No
> problem since the session set as a cookie in the client machine with that
> server name. But if you are using different webserver with servlet engine
> plugged in to that then you can't maintain the sessions. Because the session
> information is with respect to the server. Other server can't access that
> information. Sometimes back I got this problem and after that I changed
> everything in to form-hidden parameters and also I used request dispatcher
> method.
This doesn't have to be the case. If you set a domain-wide cookie, then
a 'well-behaving' client will send along that cookie with every request
it sends to every machine in that domain. This may or may not be what
you want.
This is not a server issue. This is not a servlet issue. See RFC 2965
(eg: ftp://ftp.isi.edu/in-notes/rfc2965.txt)
--
Patrick Timmins
[EMAIL PROTECTED]
___________________________________________________________________________
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
