Web Socket Router
Overview
This is implementation of websocket to provide a clear way to connect to and from a websocket server. Providing tools such, methods, routes, and filters.
- Creating a new instance of the Web Socket Router
By creating a new instance of the web socket router and passing to the constructor the built-in-web-socket-instance, you are able to start subscribing and sending messages.
var webSocketRouterInstance = 'ws://domain:port' context;
- Sending messages
Using the message object's builder, you cand send messages to/from the server.
webSocketRouterInstance;
- Listening to messages
This way you can define a listener for the route '/artist' with action CREATE.
webSocketRouterInstance;
- Routes Interceptors
You can also intercept messages to do error checking.
webSocketRouterInstance;
webSocketRouterInstance;
webSocketRouterInstance;
- Defining filters
This way you can define a listener for the route '/artist' with action CREATE filtering by the name Pearl Jam. Filters will apply to any first-child key of the data object.
webSocketRouterInstance;
- Pre and post message Events This Way you can define an event before sending any route containing '/artist'.
webSocketRouterInstance;
And post send events.
webSocketRouterInstance;
- Binding a different context for the listener. Even when you can defined a default context on the Web Socket Constructor, you can also define a custom execution context for the function.
webSocketRouterInstance;
The message-builder object.
Empty message
webSocketRouterInstance;
Empty data to artist on default Action
webSocketRouterInstance;
Custom data to artist with DELETE action
webSocketRouterInstance;
Custom data to artist with custom action
webSocketRouterInstance;
Listener Object
- The message-builder object.
Empty data to artist on default Action - Listener
webSocketRouterInstance;
Custom data to artist with DELETE action - Listener (Delete action its predefined and has a .delete method).
webSocketRouterInstance;
Custom data to artist with custom action - Listener (Custom actions needs to use the .on method and specify the action name).
webSocketRouterInstanceaction'myCustomAction';