...
[15:43:09 CDT(-0500)] <EricDalquist> it just appends that value to the jsessionid I believe
[15:48:37 CDT(-0500)] <EricDalquist> so jwennmacher I think I have a fix
[15:48:39 CDT(-0500)] <jwennmacher> OK. I glanced through the info. Thanks for pointing it out to me. The concept sounds fine. I think it answers my question for at least some scenarios. If using tomcat's clustering approach (software-based clustering), the use of the jvmroute will ensure that if request #1 creates the http session, request #2 will go back to the same server because of this route indication (if I'm following it right).
[15:48:42 CDT(-0500)] <EricDalquist> pushing it out locally now
[15:48:53 CDT(-0500)] <EricDalquist> and I'll push it into jasig's repo tomorrow morning
[15:49:00 CDT(-0500)] <jwennmacher> sounds great.
[15:52:48 CDT(-0500)] <jwennmacher> So I guess the scenario I'm not sure is if you have an external (hardware) load balancer and you choose to use an http header field like JSESSIONID instead of IP address, if an http request comes in and I create a session and store a value into session, am I guaranteed the next request will come to the same server. I think I am if the tomcat clustering approach you mentioned is used, or if a load balancer is set for IP-bas
[15:53:19 CDT(-0500)] <EricDalquist> I think so
[15:53:24 CDT(-0500)] <EricDalquist> the session id won't change
[15:53:33 CDT(-0500)] <EricDalquist> but I have to run
[15:53:38 CDT(-0500)] <EricDalquist> see you tomorrow
[15:53:39 CDT(-0500)] <jwennmacher> OK. Thanks.
[15:53:42 CDT(-0500)] <jwennmacher> you bet