WebSocket about deepstream.io-client-cpp HOT 3 CLOSED

README: add a list of C, C++ WebSocket libraries

from deepstream.io-client-cpp.

Initially, I decided to use WebSocket++ because

• header-only,
• BSD or Boost license,
• single purpose, and
• many stars and forks on GitHub.
  WebSocket++ immediately revealed a few code smells:
• holey documentation,
• manual initialization in a language with constructors ([example)[https://github.com/zaphoyd/websocketpp/blob/378437aecdcb1dfe62096ffd5d944bf1f640ccc3/examples/scratch_client/scratch_client.cpp#L119-L120]),
• implementation-dependent initialization although templates are used (see previous example).

With POCO C++ libraries, setting up a client takes four (or six short) lines of code.

from deepstream.io-client-cpp.

Can you also mention the interface you are going for when integrating the websocket library?

Since all websocket libraries use the

open
close
error
message

callbacks I would recommend something along the lines of ( in total pseduo code):

create( String: url to connect to )
open()
close()
send(String: as a string message)

onOpen(handler) -> handler call doesn't need arguments
onClose(handler) -> handler call doesn't need arguments
onError(handler) -> error message argument
onMessage(handler) -> Single string message argument

Integration wise, I would inject it into the connection class when the client is first created. This will give the connection class full control, and passing the connection class around is better than the entire client since it has a subset of functionality and stops unrequired methods being potentially exposed on the client object.

from deepstream.io-client-cpp.