Specifying a custom draft list on the server side is buggy!!

[Davidiusdadi]

Unfortunately specifying a custom on the server side is buggy.

Thats because EVERY single Websocket demands its own draft object (the draft object caches incomplete received frames)! Therefore draft objects must not be shared!

To fix that the draft object has to be cloned before use...

I will fix that as soon as i have time which will be within the next few days.

Usually you only create one client at once therefore you won't get trouble there .

#132 @Joris-van-der-Wel FYI

[Joris-van-der-Wel]

Thanks.

I was actually already creating a new one for every connection in my own code so that it matches what the constructor does.

This was by accident because I wrote my own WebSocketServer class so that the library would work in conjunction with an existing http server.