[
https://issues.apache.org/jira/browse/WICKET-4832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikko Tiihonen updated WICKET-4832:
-----------------------------------
Attachment: WICKET-4832-websocket-broadcast.patch
First draft of working websocket broadcast
> Websocket broadcast support
> ---------------------------
>
> Key: WICKET-4832
> URL: https://issues.apache.org/jira/browse/WICKET-4832
> Project: Wicket
> Issue Type: New Feature
> Components: wicket-native-websocket
> Affects Versions: 6.2.0
> Reporter: Mikko Tiihonen
> Assignee: Martin Grigorov
> Labels: websocket
> Attachments: WICKET-4832-websocket-broadcast.patch
>
>
> The attached patch provides a way to do push events outside of wicket.
> Current native websocket support only allows pushing wicket components to
> browser as a response to ajax or websocket message. With this feature it is
> possible to push external event for processing in wicket context so that
> wicket code can normally update components, which are then pushed over
> websocket connection to the browser.
> The new api in WebSocketPushBroadcaster can be used in two ways:
> a) push to specific websocket connection
> b) broadcast push to all websockets connected to specific Page
> When either is invoked:
> 1) a new wicket context is created
> 2) a new wicket event with a IWebSocketPushMessage is broadcast to relevant
> components
> 3) the components are added to the event
> 4) the modified components are pushed to browser over websocket connection
--
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
