One potential problem with frames is the session id if cookies are disabled.
Just one Scenario: - Create a page with two independend frames Each page contains a url encoded link - Visit the page - Wait <SessionTimeOut> + some seconds - Follow the link in one window the original session is not a valid session anymore, so tomcat creates a new session with a new session id. - Follow the link in the other window the original session is still not a valid session, and tomcat 'forgot' that it just created a new session so tomcat creates a new session with a new session id. - Now you have one session in each window Another Scenario: - Create a page with two frames, where one frame contains two urlencoded links with the other frame as target, the other frame displays something depending on which link you clicked in the navigation frame. - Wait <SessionTimeOut> + some seconds - The sessionid for the links times out, and from that on each time you click in the navigation frame you get a new session in the second frame. > -----Ursprüngliche Nachricht----- > Von: Larry Isaacs [mailto:[EMAIL PROTECTED]] > Gesendet: Donnerstag, 17. Januar 2002 14:28 > An: 'Tomcat Users List' > Betreff: RE: Urgent: works on TC 3.2.2, but not on TC 3.3 !!! > > > Usually frames are involved when something like this happens. > My involvement with Tomcat is through an IDE I work on, so > I haven't done a lot of real world webapp development. Thus, > I don't know why the frames get different sessions. I would > expect them to get the same session as the main page. When > I get a chance, I'll try to do some experimentation and see > if there is something that can be done. > > Cheers, > Larry -- To unsubscribe: <mailto:[EMAIL PROTECTED]> For additional commands: <mailto:[EMAIL PROTECTED]> Troubles with the list: <mailto:[EMAIL PROTECTED]>
