You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
WO apps get WebSockets and SSE from wo-adaptor-jetty-push (about 1,000 lines). ng should offer the same API so push code moves between the frameworks unchanged: one framework-neutral library both can use, with a thin shim on each side.
The neutral core (no framework dependency)
WebSocket session: send text or binary, close, attributes, remote address. WOWebSocketSession is already neutral apart from its name.
Handler: an interface with default no-op methods (onConnect, onTextMessage, onBinaryMessage, onClose, onError). It replaces the abstract WOWebSocketHandler.
application() isn't needed; both frameworks have a static one.
Heartbeat becomes a small utility instead of an executor in the base class.
Handshake: a small record (path, query, headers, cookies, remote address) passed to onConnect instead of a framework request.
SSE:SSEStream (event formatting, keep-alive, the blocking stream) and SSEHub. Both are neutral except SSEStream.response().
No registration mechanism: each framework maps endpoints its own way.
Both adaptors are on Jetty 12.1.13, so the Jetty WebSocket glue (listener, session wrapper) can be shared too.
WO shim (in wo-adaptor-jetty-push)
Keeps WOWebSocketRegistry, the upgrade wiring through JettyHandlerDecorator, and a handler variant that receives the WORequest.
Activity