> Transport session tracks sessions using HTTP session IDs. In this case, > the session ID is originated at the server side (as opposed to the > client side generated session IDs in ClientID sessions). Server > generates an HTTP session ID for the first request from the client. And > it includes that ID as a HTTP header in the response to the client. Then > client should send that session ID for all subsequent requests. > > If the ESB load balancing operates in the transport/http mode, it maps > these session IDs to endpoints (servers). So the first request from a > client can be directed to any listed endpoint (under the load balancing > configuration). Upon receiving the first response from that endpoint, > the client is bound to that endpoint. So that all > subsequent requests from that client will be sent to the same endpoint. > > SOAP mode load balancing also works with a server generated session ID. > Exception is that the session ID is sent as a SOAP header, instead of an > HTTP header.
Hi Chatura, thank you very much for your clear and precise explanation! Having read this description also the names sound quite intuitive to me. ;-) Maybe you could include this exact explanation to your documentation including the method specific header line (at least the parameter name). Regards, Eric _______________________________________________ Esb-java-user mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/esb-java-user
