Issues when running multiple sicksync instances

[laggingreflex]

If you have two sicksync instances they seem to interfere with one another's operation, when one of them sees a file change another one gets disconnected.

There's also that re-connection issue (related #51) that it re-connects multiple times so after a while you see loads of connections:

[REMOTE] [LOCAL] Connected server not using encryption
[REMOTE] [LOCAL] Connected server not using encryption
[REMOTE] [LOCAL] Connected server not using encryption
[REMOTE] [LOCAL] Connected server not using encryption
[REMOTE] [LOCAL] Connected server not using encryption
[REMOTE] [LOCAL] Connected server not using encryption
[REMOTE] [LOCAL] Connected server not using encryption
… (about >50)
^CTerminate batch job (Y/N)? ^C

PS: Both instances are to the same remote. Haven't checked with different remotes.

[laggingreflex]

Ohh, it was because they were using the same websocketPort 8675.

[joelgriffith]

Nice find!

[laggingreflex]

This is still definitely a problem, causing #67