I recently got web-socket-js set up and working. So far it seems to work pretty well as a drop-in replacement for standard WebSockets, so congratulations on your hard work.
I did notice that when close() is called on the client, it sends 0xff and 0x00 before terminating the connection. I looked at the draft 76 spec, and it mentions that the server is the one that should be sending this to the client, not the other way around.
I recently got web-socket-js set up and working. So far it seems to work pretty well as a drop-in replacement for standard WebSockets, so congratulations on your hard work.
I did notice that when close() is called on the client, it sends 0xff and 0x00 before terminating the connection. I looked at the draft 76 spec, and it mentions that the server is the one that should be sending this to the client, not the other way around.