On 9/10/07, Christopher Schultz <[EMAIL PROTECTED]> wrote: > Thomas Gelzhaeuser wrote: > > - if the session identifier is known - use the session for the request > > with which the session was started. > > You can make any request to a Tomcat server using a session id encoded > in the URL like this: > > http://host/resource;jsessionid=[sessionid] > > This will act just like any other client, and if the session id is > valid, it will be used. > > > - if the session identifier is unknown - start a new session on the > > requested webapp (with a predefined session timeout to prevent wasting > > resources) > > Do you mean that you want Tomcat to use the session id provided after > creating it? Tomcat doesn't do this... if you request an invalid session > id, you'll get a new session with an unrelated session id.
Hi Chris. Thanks for your answer. I guess I have to clarify my situation here a bit: We are creating an application which will run as a kind of slave to another (for us completely unknown) application server. This server has a kind of custom session handling and all it can provide to us is an identifier of the session used by that server. Thus we need to mimik somehow the session handling provided by the other server. The open question for me ist where the entry point to such a thing is (I think it's quite improbable that we are the first ones actually trying to solve a problem like this) Thanks. Thomas. --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
