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 2013/11/26 09:13:38 UTC

[jira] [Resolved] (WICKET-5367) migrate Wicket-Atmosphere to Atmosphere 2

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

Emond Papegaaij resolved WICKET-5367.
-------------------------------------

       Resolution: Fixed
    Fix Version/s: 7.0.0
                   6.13.0

Atmosphere is upgraded to 2.0.4 and the JS to 2.0.8.

> migrate Wicket-Atmosphere to Atmosphere 2
> -----------------------------------------
>
>                 Key: WICKET-5367
>                 URL: https://issues.apache.org/jira/browse/WICKET-5367
>             Project: Wicket
>          Issue Type: Improvement
>          Components: wicket-atmosphere
>    Affects Versions: 6.10.0
>            Reporter: Zala Goupil
>            Assignee: Emond Papegaaij
>              Labels: features
>             Fix For: 6.13.0, 7.0.0
>
>
> As Atmosphere 2 provides lots of performance & memory-management improvements (as JF Arcand says),  amongst other things, I think it would be great to migrate Wicket-Atmosphere to the last Atmosphere stable version.



--
This message was sent by Atlassian JIRA
(v6.1#6144)