Closed bob-nl closed 10 years ago
A WebSocket server is similar to the client, after the initial handshake completes. The difference is in the logic for the initial handshake: the server must parse the GET request, look for the Upgrade: websocket
header, implement a sha1 hash, and base64 encoding. Is this something you'd like to see easywsclient doing?
I like the fact that easywsclient is so small and does not need boost. This is why it would be nice to use this lightweight web socket implementation for web socket hosting. But at this moment i will not use it since IMO it has not matured enough. I did try the web socket client and it works nice. I look forward to how it develops.
@bob-nl the feedback is appreciated, thanks. Any constructive input you have is valued.
P.S.- Are you going under multiple github aliases?
@bob-nl, I would like to inform you that the fact that you are posting using a pseudonym that you "will not use [easywsclient] since IMO it has not matured enough" will not lead to me accepting your bogus patch #35. The only thing that will change this outcome is a quality contribution.
Would it be difficult to create a easywsserver? What would have to be changed to this code to do this?