[
https://issues.apache.org/jira/browse/WICKET-6358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16030759#comment-16030759
]
ASF subversion and git services commented on WICKET-6358:
---------------------------------------------------------
Commit 2bb5ad6bc0845bbde298644c14f906407bdef82f in wicket's branch
refs/heads/wicket-7.x from [~mgrigorov]
[ https://git-wip-us.apache.org/repos/asf?p=wicket.git;h=2bb5ad6 ]
WICKET-6358 Possibility for each browser tab to have independent wicket session
Introduce overrideable methods for setting and getting the Wicket Session in
HttpSession
(cherry picked from commit d8206a23ca79ca66b3b9a0e53e2ccfe854b94b16)
> 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
>
> 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)
