-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Ivo,
On 7/9/2009 6:32 AM, Ivo Silva wrote: > To both browser and Tomcat it's only one session. My filter is what > manages the "nested" sessions distribution and that's why an > identifier is required. > > Each iframe should have it's own session since the application stores > data on session. If I do not provide different sessions the variables > would overwrite each other and each iframe would have the same > information. What if you used a request parameter instead of request path info? So, to re-state, you want to take the following URLs and make them serve a single page, after "unwrapping" a special session that is stored in the main session: /context/X/page_1.jsp /context/Y/page_1.jsp /context/Z/page_1.jsp ?? I still don't understand why the URL rewriting is necessary, though I *do* understand the session multiplexing (which is a total PITA, BTW). - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkpY+gEACgkQ9CaO5/Lv0PBBSgCePoHoEKENfgUJGLdQe4O90Zjr xcYAn11zYGYzlnlWHwib0bA8O7O8RtYy =XEcl -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
