[jira] [Commented] (WICKET-6358) Possibility for each browser tab to have independent wicket session

["Martin Grigorov (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/WICKET-6358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16034450#comment-16034450 ] 

Martin Grigorov commented on WICKET-6358:
-----------------------------------------

[~mmakundi]
The cookie is used to send the custom session id with every request.
The custom session id is stored in sessionStorage which is unique per tab.

[~Claudia Hirt]:
The second tab will start with its own session. That's the idea here.
If you want to keep the session from the first tab then you should store the custom session id in the sessionStorage when rendering the second page for first time.

Please make sure you describe the steps to reproduce your issue when providing your applications. 

> Possibility for each browser tab to have independent wicket session
> -------------------------------------------------------------------
>
>                 Key: WICKET-6358
>                 URL: https://issues.apache.org/jira/browse/WICKET-6358
>             Project: Wicket
>          Issue Type: Improvement
>          Components: wicket
>    Affects Versions: 8.0.0-M5
>            Reporter: Martin Makundi
>            Assignee: Martin Grigorov
>         Attachments: Wicket_Quickstart_7.zip
>
>
> Here are a couple of discussions on the topic:
> https://myfaces.apache.org/orchestra/myfaces-orchestra-core/multiwindow.html
> http://stackoverflow.com/questions/368653/how-to-differ-sessions-in-browser-tabs
> http://stackoverflow.com/questions/4970004/support-multiple-browser-tab-session-j2ee-web-application
> Currently in wicket if user wants to safely use two browser windows in the same application, they must login from different browsers (or use some suitable browser-specific private browsing mode).
> We would like to add functionality into wicket to allow:
> - automatic detection of new browser tab
> - configuration option which would keep independent wicketsession for each browser tab (initially clone from wicketsession of window that opened new tab)
> - possible solution: pagemap and wicketsession could go hand in hand, each pagemap with its own wicketsession to keep them insulated
> We'll start working on this immediately, all suggestions welcome.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)