Details

      Description

      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

        Issue Links

          Activity

          Hide
          Mikko Tiihonen added a comment -

          First draft of working websocket broadcast

          Show
          Mikko Tiihonen added a comment - First draft of working websocket broadcast
          Hide
          Martin Grigorov added a comment -

          Thank you for your contribution!
          The patch is applied with some improvements. Please check them and give us feedback if something can be improved further.

          Show
          Martin Grigorov added a comment - Thank you for your contribution! The patch is applied with some improvements. Please check them and give us feedback if something can be improved further.

            People

            • Assignee:
              Martin Grigorov
              Reporter:
              Mikko Tiihonen
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development