You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Daniel Stoch (JIRA)" <ji...@apache.org> on 2014/06/12 17:07:01 UTC

[jira] [Updated] (WICKET-4657) Avoid losing events between instantiation and rendering

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

Daniel Stoch updated WICKET-4657:
---------------------------------

    Attachment: PageTasksScheduler.zip

> Avoid losing events between instantiation and rendering
> -------------------------------------------------------
>
>                 Key: WICKET-4657
>                 URL: https://issues.apache.org/jira/browse/WICKET-4657
>             Project: Wicket
>          Issue Type: Wish
>          Components: wicket-atmosphere
>    Affects Versions: 6.0.0-beta3
>            Reporter: Pouyan Zaxar
>            Assignee: Emond Papegaaij
>         Attachments: PageTasksScheduler.zip
>
>   Original Estimate: 4h
>  Remaining Estimate: 4h
>
> Currently the atmosphere module subscribes components to the EventBus just before they are rendered. Naturally events sent on the EventBus before component rendering are lost. You cannot even save lost events using a BoradcasterCache (https://github.com/Atmosphere/atmosphere/wiki/Understanding-BroadcasterCache).
> It could be advantageous if components are registered on instantiation (just before initialization) and it can be set if the component wants to receive cached events (e.g. @Subscribe(cache=true)) which have been generated between registering and rendering of the component.



--
This message was sent by Atlassian JIRA
(v6.2#6252)