Apache Wicket 8.x Reference GuideWebSocketBehavior.onMessage() or WebSocketResource.onMessage() where the application logic can react on it. The server can push plain text and binary data to the client, but it can also add components (Wicket.Event PubSub). Once a page that contributes (Base)WebSocketBehavior is rendered the client may react on messages pushed by the server by subscribing to the '/websocket/message' event: Wicket.Event0 码力 | 350 页 | 9.95 MB | 1 年前3- Apache Wicket 7.x Reference GuideWebSocketBehavior1.onMessage() or WebSocketResource1.onMessage() where the application logic can react on it. The server can push plain text and binary data to the client, but it can also add components (Wicket.Event PubSub). Once a page that contributes (Base)WebSocketBehavior is rendered the client may react on messages pushed by the server by subscribing to the '/websocket/message' event: Wicket.Event0 码力 | 346 页 | 10.00 MB | 1 年前3
- Apache Wicket 10.x Reference GuideWebSocketBehavior.onMessage() or WebSocketResource.onMessage() where the application logic can react on it. The server can push plain text and binary data to the client, but it can also add components (Wicket.Event PubSub). Once a page that contributes (Base)WebSocketBehavior is rendered the client may react on messages pushed by the server by subscribing to the '/websocket/message' event: Wicket.Event0 码力 | 336 页 | 7.16 MB | 1 年前3
- Apache Wicket 9.x Reference GuideWebSocketBehavior.onMessage() or WebSocketResource.onMessage() where the application logic can react on it. The server can push plain text and binary data to the client, but it can also add components (Wicket.Event PubSub). Once a page that contributes (Base)WebSocketBehavior is rendered the client may react on messages pushed by the server by subscribing to the '/websocket/message' event: Wicket.Event0 码力 | 335 页 | 7.15 MB | 1 年前3
共 4 条
- 1