Recover from failed socket connection

[anthonywebb]

The other day, for some reason the socket between cgate-client.js and my cgate server failed. When that happens, the client will log errors, but we dont yet have any way to recover/recycle the connection again. This would be a nice addition.

I am attaching some screenshots of what my logs look like when I did hit that failed socket. Once the socket was failed anything I would try to do over that socket was failing and being logged.

[simonhac]

@anthonywebb i'm sure there is a better way of doing this, but in the meantime, this should work:

• upon unexpected close of any of the command, event or status sockets, throw an exception that kills the server
• use the forever module to keep the service available

[simonhac]

@anthonywebb i'm in this code, so i'm happy to look into this.

[simonhac]

@anthonywebb i'm enjoying using template literals from ES6. do you know if there is any issue with using ES6 language features and nodejs? (ie. can i expect that all nodejs runtime instances will support ES6?)

(i'm very new to this, but i can see from node.green that template literals have worked in node.js since v5.11.1, which was released 2016-05-05.)

[simonhac]

@anthonywebb please assign me to this (or let me know how i can assign myself).

[anthonywebb]

@simonhac it wont let me officiall assign you for some reason. Feel free to take it on though! 👍

[simonhac]

thanks @anthonywebb -- i'm new to this, but i think this article explains how to assign to me.

[simonhac]

fixed in v0.5.8 (PR #27)