-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Simon,
Simon Papillon wrote: | I'll check this out, I think you could be right, it will probably lead | to a lumpy load profile accross the tomcat servers, but I might give | it a go. Yeah, but a lumpy load profile that works properly is better than a flat load profile that doesn't. ;) | I set a tracking gif on each page pointing to a single domain e.g. | tracker.first-domain.com this is served up by the same container | as an query string argument I pass in the jsessionid for whichever | domain the request is made to. [snip] | the servlet handling the tracker.first-domain.com/track.gif registers | the different domain specific session ids with its own session id and | thus ties them altogether, thus when one of the session ids logs on, | its associated with a tracker session id which can then propogate the | information to the other user sessions. Wow, does that really work? That's a tremendously cool hack, if so! TC should not be respecting the JSESSIONID passed-in if it is invalid. Perhaps I'm misunderstanding you, though. Do you have a registry of session ids cross-linked in the session of each web application? - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkhSlpUACgkQ9CaO5/Lv0PD5TgCgn9+hn8fghSynKnzJQ4c68mxi ufsAn1MM1S3nI+R4e4baKlBqN/MhtgyC =codo -----END PGP SIGNATURE----- --------------------------------------------------------------------- To start a new topic, e-mail: [email protected] To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
