swampyer

A lightweight WAMP client that implements the WAMP v2 basic profile

The library is highly promise based. Almost all available operations return a promise. However, it also allows for subscription to various events useful for monitoring the lifecycle of the WAMP connection.

API documentation

Installation

npm i swampyer

Examples

• Open an unauthenticated connection without any automatic reconnection

  import { Swampyer } from 'swampyer';
  import { WebsocketJson } from 'swampyer/lib/transports/websocket_json';
  
  //...
  
  const wamp = new Swampyer();
  await wamp.open(new WebsocketJson('ws://localhost:8080/ws'), { realm: 'realm1' });
  
  // Use the `wamp` object for the WAMP operations

• Open an authenticated connection without any automatic reconnection

  import { Swampyer } from 'swampyer';
  import { WebsocketJson } from 'swampyer/lib/transports/websocket_json';
  
  //...
  
  const wamp = new Swampyer();
  await this.wamp.open(new WebsocketJson('ws://localhost:8080/ws'), {
    realm: 'realm1',
    auth: {
      authId: '<some username here>',
      authMethods: ['ticket'],
      onChallenge: method => '<authentication for the user>',
    }
  });
  
  // Use the `wamp` object for the WAMP operations

• Open an auto reconnecting unauthenticated connection. If the connection can not be established on the first try or if the connection closes for some reason, then it will keep trying to reconnect until it succeeds or wamp.close() is called.

  import { Swampyer } from 'swampyer';
  import { WebsocketJson } from 'swampyer/lib/transports/websocket_json';
  
  //...
  
  const wamp = new Swampyer();
  this.wamp.openAutoReconnect(
    () => new WebsocketJson('ws://localhost:8080/ws')
    { realm: 'realm1' }
  );
  
  wamp.openEvent.addEventListener(() => {
    // Use the `wamp` object for the WAMP operations
  });

• By default, the delay between each successive reconnection attempt increases pseudo-exponentially starting from 1ms up to a maximum of 32000ms. The following example sets the delay between reconnection attempts to 1000ms and stops the reconnection process on the 4th attmept

  import { Swampyer } from 'swampyer';
  import { WebsocketJson } from 'swampyer/lib/transports/websocket_json';
  
  //...
  
  const wamp = new Swampyer();
  this.wamp.openAutoReconnect(
    () => new WebsocketJson('ws://localhost:8080/ws')
    {
      realm: 'realm1',
      autoReconnectionDelay: () => 1000,
      stopAutoReconnection: (attempt) => attempt >= 4,
    }
  );
  
  wamp.openEvent.addEventListener(() => {
    // Use the `wamp` object for the WAMP operations
  });

Usage on nodejs

Some adjustments need to be made in order to get this library working in a Nodejs environment:

• Install a websocket implementation for nodejs (here we use ws as an examples)

• Run the following at the start of you nodejs code

  const ws = require('ws');
  
  // Other imports ...
  
  global.WebSocket = ws;
  
  // Any code that uses Swampyer ...

  • This will allow WebsocketJson transport provider to work properly in the node environment

Transport Providers

The core library only concerns itself with sending and handling WAMP protocol messages. The method of transporting the WAMP messages to and from a WAMP server, and the serialization/deserialization process is left up to the user. The user must provide a transport provider to the open() method in order to establish a successful WAMP connection.

The library optionally provides WebsocketJson which is a transport provider that allows connection over Websockets and uses JSON to serialize/deserialize the data. This transport provider should satisfy the needs for most users as most WAMP servers communicate over websocket and use the JSON format for the messages.

Custom Transport providers

If a custom transport method or serialization method is required, then the library allows the user to easily create their own custom transport providers.

Custom transport providers must be a class that implements the TransportProvider interface. This ensures that the class implements all the functions that the library needs in order to make use of the transport provider.

See the implementation of WebsocketJson to get an idea of how to implement your own custom transport provider.