jri at deepamehta.de
So Jan 12 01:18:26 CET 2014
On Jan 7, 2014, at 4:40, Jörg Richter wrote:
> Next possible step from my side:
> - Make the dm4-websockets plugin extensible by 3rd party plugin developers. That is abstracting the WebSocket server (and the Jetty API) away and provide the plugin developer a framework for handling client-side and server-side WebSocket messages.
The dm4-websockets plugin is now extensible by 3rd party plugin developers. That is your plugin can rely on the facilities provided by the dm4-websockets plugin, which basically are:
- a WebSocket server running on port 8081, usable by several plugins at the same time.
- a service to let your plugin broadcast messages to WebSocket clients (server push).
- server-side events to let your plugin react upon incoming WebSocket messages.
For illustrative purposes there is a WebSockets example application. It performs mainly the example task described before: broadcasting topic update events to all connected WebSocket clients.
So, DM is now ready for server push applications.
However, it's just the first incarnation. If your plugin needs more elaborated WebSocket features don't hesitate and post here.
Mehr Informationen über die Mailingliste devel