The Hydra-Router supports WebSocket connections. However, it only accepts stringified UMF formatted messages.

let ws = new WebSocket('ws://');
ws.on('open', () => {
  let msg = {
    'to': 'a-hydra-service:/',
    'version': 'UMF/1.4.3',
    'from': 'tester:/',
    'mid': '4736ef3d-fcbb-46aa-80a0-f4f3493e1d74',
    'timestamp': '2017-01-12T20:16:29.157Z',
    'body': {}

WebSocket reconnection and messaging

Hydra-Router supports queuing messages intended for your WebSocket client should your client's WebSocket connection break. Your client only needs to reconnect and issues a reconnection message to begin receiving earlier messages.

Upon an initial connection your WebSocket client will receive a message that looks a bit like this:

  "to": "2945p8eigxz@client:/",
  "frm": "c274b25909aee5cbec2857361f425fa7@hydra-router:/",
  "mid": "dffc2949-0e2a-4417-8f28-46addb5fc716",
  "ts": "2017-01-12T19:31:54.831Z",
  "typ": "connection",
  "ver": "UMF/1.4.3",
  "bdy": {
    "id": "2945p8eigxz"

Thebdy.idvalue is the WebSocket session ID. If your client dies and needs to reconnect it can issue a reconnection message such as:

  "to": "hydra-router:/",
  "frm": "client:/",
  "mid": "e173a0da-2785-4f83-8b39-0dea954dd91b",
  "typ": "reconnection",
  "ver": "UMF/1.4.3",
  "bdy": {
    "id": "2945p8eigxz"

There are three things to note above. First the message is sent to thehydra-routerwhich manages the actual WebSocket connections. Secondarily, thebdy.idis the same as the WebSocket session ID that the client had before it crashed or lost its connection. Thirdly, we use a message type (typ) of "reconnection".

Upon receiving a message like that, Hydra-Router will load queued messages (if any) and begin sending them to your newly connected client.

Example program repos

You can see the new reconnection logic by trying the following two examples.

To try this you need to have both Redis and a hydra-router running locally. You then start a copy of themessage-echo-servicewhich will essentially relay messages to a sender. Themessage-sender-servicesends message to the echo service.

You can terminate the sender at some point and then restart it using theidof the first connection response.

$ node message-sender-service 1fh5zi3fglr

That will put the sender app into a reconnection and retrieval mode.

results matching ""

    No results matching ""