sharing websockets for node and the browser isomorphically. Use between different node modules or components for react, flux, reflux, webpack or browserify


Keywords
react, react.js, reactjs, websocket, websockets, web, socket, sockets, share, shared, sharing, ws, list, common, flux, reflux, component, components, store, stores, action, actions, vanilla
License
Other
Install
npm install ws-share@2.0.2

Documentation

ws-share

A module allowing isomorphic sharing of websockets between different functions, modules, scripts, actions, stores, and/or components with vanilla js (plain js), react, webpack or browserify. This module is brand new, don't hold its lack of stats and install against it, give it a shot!

npm ws-share info : See npm trends and stats for ws-share
Package Quality
ws-share npm version supported node version for ws-share total npm downloads for ws-share monthly npm downloads for ws-share npm licence for ws-share

npm install --save ws-share

RIAEvangelist

GitHub info :
ws-share GitHub Release GitHub license ws-share license open issues for ws-share on GitHub

ws-share site

What does ws-share do?

ws-share extends and normalizes both node ws and the browser WebSocket normalizing events and manages of a list of open websockets and protocols allowing websockets to be easily shared between multiple vanilla js (plain js), or common js modules. Each module can create a new WS instance for a given uri and protocol. However, if a socket with that uri & protocol list has already been opened, WS will reference the open socket instead of creating a new socket for the same uri and protocol list.

ws-share is designed to feel like you are naturally working with a standard WebSocket

ws-share makes your WebSocket code isomorphic, the same code will run both in node AND in the browser!

Tips

For vanilla js (just plain old js) include the browser.js file

<script src='ws-share-vanilla.js' />

You should check ws.readyState upon creation.

Why?

If the shared websocket was already opened ws.on('open',callback) wont be called. So checking the ready state will allow you to perform any initialization needed in your node module, browser code, react component, action or store.

Everything normally available on the WebSocket is available plus the normalized methods and members added to the shared WebSockets below, this helps your code stay isomorphic so it can run on the server and browser :

method or value type mutable description
uri string false the uri of the shared ws
protocols array/string false the protocols of the shared ws
on func false bind event listener to shared websocket
off func false UNbind event listener to shared websocket

Contributing

  1. Pull or Fork code.
  2. from the cloned directory run npm install (this will install required dependencies, depending on your system may require)
  3. be awesome!

Running Example React Shared WebSocket Echo App

This very basic react.js example app has two components share the same websocket. Neither is aware they are sharing though. The Input component sends info upto the server while the Output listens for messages from the server. The websocket.org server here just echo's all information back for demo purposes.

Browser

  1. npm install
  2. npm start echo
  3. goto localhost:8080
  4. type some stuff and watch both components use the same websocket

Node

  1. node examples/echo/node/echo.js

Create or Use Existing Shared WebSocket

This follows the standard WebSocket interface.

    //commonjs
    var WS=require('ws-share');
    //or vanilla js
    <script src='ws-share-vanilla.js' />


    var basicWS=new WS('wss://echo.websocket.org/?encoding=text');

    var wsWithOneProtocol=new WS('wss://echo.websocket.org/?encoding=text','stream');

    var wsWithManyProtocols=new WS(
        'wss://echo.websocket.org/?encoding=text',
        [
            'stream',
            'chat',
            'whatever'
        ]
    );

Bind Events on a Shared WebSocket

This follows the standard WebSocket interface and also extends that interface with .on and .off as shortcuts for .addEventListener and .removeEventListener as on/off is commonly used in node applications and may be more intuitive for some developers. All standard events are supported. Remember the scope of your callback is the shared websocket! if you want to use the react modules scope use .bind(this) on the callback

    //commonjs
    var WS=require('ws-share');
    //or vanilla js
    <script src='ws-share-vanilla.js' />

    var ws=new WS('wss://echo.websocket.org/?encoding=text');

    ws.on(
        'open',
        function(e){
            console.log('shared websocket open!');
        }
    )

    ws.on(
        'close',
        function(e){
            console.log('shared websocket closed!');
        }
    )

    ws.on(
        'error',
        function(e){
            console.log('OMG there\'s been an error!',e);
        }
    )

    ws.on(
        'message',
        function(e){
            console.log('got message on shared ws!',e.data);
        }
    )

Basic Example :

You will notice this looks just like a standard websocket creation, but behind the scenes it stores a refrence to share with any other component, store, or action which may also need access to this same websocket.

    //commonjs
    var WS=require('ws-share');
    //or vanilla js
    <script src='ws-share-vanilla.js' />

    var ws=new WS('wss://echo.websocket.org/?encoding=text');
    ws.on(
        'message',
        function(e){
            console.log(e.data);
        }
    );

Basic Node Example :

    var WS=require('ws-share');

    var ws=new WS('wss://echo.websocket.org/?encoding=text');

    ws.on(
       'open',
       function(){
           ws.send('hello world!');
       }
    );

    ws.on(
        'message',
        function (message){
            console.log(message);
        }
    );

    ws.on(
        'error',
        function (err){
            console.log('error encountered :', err);
        }
    );

Basic React Send Example :

You will notice this looks just like a standard websocket creation, but behind the scenes it stores a refrence to share with any other component, store, or action which may also need access to this same websocket. For example, the next example, Output would share this same ws without needing a different format.

    var React=require('react');
    var WS=require('ws-share');

    var Input=React.createClass(
        {
            componentWillMount:function(){
                this.ws=new WS('wss://echo.websocket.org/?encoding=text');
            },
            componentWillUnmount:function(){
                this.ws=null;
            },
            _change:function(e){
                if(this.ws.readyState!==1){
                    console.log('WS not yet connected or already disconnected. Can not send message.');
                    return;
                }
                this.ws.send(e.target.value);
            },
            render:function(){
                return (
                    <div>
                        <h3>
                            Send To Server
                        </h3>
                        <input onChange={this._change} />
                    </div>
                )
            }
        }
    );

    module.exports=Input;

Basic React Listen for Message Example :

You will notice this looks just like a standard websocket creation, but behind the scenes it stores a refrence to share with any other component, store, or action which may also need access to this same websocket. For example, the previous example, Input would share this same ws without needing a different format.

    var React=require('react');
    var WS=require('ws-share');

    var Output=React.createClass(
        {
            getInitialState:function(){
                return {
                    message:''
                }
            },
            componentWillMount:function(){
                this.ws=new WS('wss://echo.websocket.org/?encoding=text');
                this.ws.on(
                    'message',
                    function(e){
                        this.setState(
                            {
                                message:e.data
                            }
                        )
                    //We want to use this.state,
                    //so we have to bind the react component
                    //scope to the callback
                    }.bind(this)
                );
            },
            componentWillUnmount:function(){
                this.ws=null;
            },
            _change:function(e){
                if(this.ws.readyState!==1){
                    console.log('WS not yet connected or already disconnected. Can not send message.');
                    return;
                }
                this.ws.send(e.target.value);
            },
            render:function(){
                return (
                    <div>
                        <h3>
                            Got From Server
                        </h3>
                        <textarea value={this.state.message} />
                    </div>
                )
            }
        }
    );

    module.exports=Output;


This work is licenced via the DBAD Public Licence.