Sticky session for cookiless clients

Hello, Thanks for your prompt reply I will have a look at TMM. "So the clients don't support cookies but can be configured to send a custom HTTP header with a session ID? What kind of client is this? " => It is Flex based clients or 3rd part clients using SOAP and for which we have no garanties that they accept cookies. => no the session id is not on the HTTP header but provided by the application server instance at each session issued by the client. My real concern here is to ensure not only server persistence (same session goes to the same application server instance) but session persistence (a session S1 going to application server instance ASI1 based will go at the next round trip to the same application server ASI1 AND most importantly with the same session id so the session persistence is maintained. Otherwise we loose the session). BR

 

 

Note : here by session we mean Http session.