Yeah, that is a good point. The third option - cross context disabled or remote host - will not keep session data, unless you one of three things: - the request is stateless (where it doesn't matter anyways) - you forward everything to the remote host, including the cookies and all; this seems complex to get right - you maintain a new session with state locally
I was working under the assumption that a lone request to a remote host is fully stateless. Not necessarily a fair assumption, I guess. Pid wrote: >not unless you've got clustering setup and the cluster is correctly >sharing session data. the session data is otherwise local to the server >in use. > >Vinu Varghese wrote: > > >>Avi, >>What will happen with the session and objects bound to it ?, Will they >>be accessible in the second server ? >> >>- Regards >>Vinu >> >>Avi Deitcher wrote: >> >> >>>Zohar, >>>- In the same host & context, use RequestDispatcher.forward() >>>- In the same host but different context, if cross-context enabled, get >>>the RequestDispatcher for that context then use forward() >>>- Different host entirely, or cross-context not enabled, you will >>>probably need to rebuild the request. I usually use the Jakarta Commons >>>HTTPClient for this. Check out >>>http://jakarta.apache.org/commons/httpclient/ >>> >>>Anyone have a better suggestion? >>> >>>Avi >>> >>>Zohar wrote: >>> >>> >>> >>> >>>>Hello list, >>>>I have a servlet that handles POST requests. Sometimes the request >>>>needs to be forwarded to a different servlet, which may be running on >>>>a different server. What is the best way to do that? >>>>Thanks, >>>>Zohar. >>>> >>>> >>>> >>>> >>>> >>> >>> >>> > >--------------------------------------------------------------------- >To start a new topic, e-mail: users@tomcat.apache.org >To unsubscribe, e-mail: [EMAIL PROTECTED] >For additional commands, e-mail: [EMAIL PROTECTED] > > > -- ______________________________ Avi Deitcher [EMAIL PROTECTED]
