You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Emond Papegaaij (JIRA)" <ji...@apache.org> on 2012/09/04 20:39:07 UTC

[jira] [Resolved] (WICKET-4729) atmosphere example will stop working if opening the same url in a different tab in the same browser

     [ https://issues.apache.org/jira/browse/WICKET-4729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Emond Papegaaij resolved WICKET-4729.
-------------------------------------

       Resolution: Fixed
    Fix Version/s: 6.1.0

I've reworked the page registration. The BiMap was used to make sure the registration would not grow with every page opened. I've replaced the BiMap with a normal HashMap and added a method to unregister a connection when it is closed.
                
> atmosphere example will stop working if opening the same url in a different tab in the same browser
> ---------------------------------------------------------------------------------------------------
>
>                 Key: WICKET-4729
>                 URL: https://issues.apache.org/jira/browse/WICKET-4729
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket-atmosphere
>    Affects Versions: 6.0.0-beta3
>            Reporter: Sean Lin
>            Assignee: Emond Papegaaij
>             Fix For: 6.1.0
>
>
> If the url of a running atmosphere example is copied and then opened in a different tab while the old one left open in the same browser,
> i.e. there are two atmosphere examples of the same url opened at the same time in a browser, 
> one of them will stop working.
> I found the cause of this problem is that trackingPages in EventBus is using a BiMap.
> If there are different tracking-ids mapping to the same PageKey, one of the map entry will be removed.
> The simple solution would be replacing the BiMap with HashMap, but I think there might be reasons why BiMap is used here.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira