Question #2 can be muddy depending on how the new window was launched. In my experience (Using IE 6) if you click on a link (i.e target="_blank") that launches an application and log in, then go back and click that link again to open a new window to the same application, you will be using the same wicket session - and http-session.
In the above scenerio, multi-window support does not work. If you were to launch a new window or new tab from the WICKET app browser itself, then multi-window does work and you get different sessions. So, a link opening a new window i.e. target="_blank" and physically opening a new window using the browser can get different results. -----Original Message----- From: Igor Vaynberg [mailto:igor.vaynb...@gmail.com] Sent: Sunday, July 26, 2009 2:50 PM To: users@wicket.apache.org Subject: Re: Questions about Wicket sessions On Sun, Jul 26, 2009 at 8:53 AM, David Chang<david_q_zh...@yahoo.com> wrote: > 1. If I open another tab on the same browser (IE or FF), visitor activities > on the same Wicket app are considered in the same session? same session, this is why we provide browser auto-multiwindow support, so we can detect a new tab/window being open and the app still works fine. > 2. If I start IE or FF in another window, visitor activities on the same > Wicket app are considered in the same or different session? always a different sessions, browsers do not share sessions. > 3. If dirty() is called within a method of custom session object, then it is > the developer's responsibility to implement dirty() to synchronize with other > clustered web servers, correct? no, your responsibility is only to call dirty() when you change your custom state in session. the servlet container will take care of replicating session across the cluster. -igor > > Thanks! > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ EMAIL CONFIDENTIALITY NOTICE This Email message, and any attachments, may contain confidential patient health information that is legally protected. This information is intended only for the use of the individual or entity named above. The authorized recipient of this information is prohibited from disclosing this information to any other party unless required to do so by law or regulation and is required to destroy the information after its stated need has been fulfilled. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or action taken in reliance on the contents of this message is strictly prohibited. If you have received this information in error, please notify the sender immediately by replying to this message and delete the message from your system. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
