3 ms·

Another option is gwsocket[1] >>> gwsocket is a simple, standalone, language-agnostic, RFC6455 compliant WebSocket Server, written in C. It sits between your a

by fasteo 5y ago

Another option is gwsocket[1] >>> gwsocket is a simple, standalone, language-agnostic, RFC6455 compliant WebSocket Server, written in C. It sits between your application and the client's browser, giving fast bidirectional communication between these two with ease and flexibility [1] https://gwsocket.io/man https://gwsocket.io/man

cloudyglider 5y ago
Do any of these options support communicating via an http API instead of stdin/out? Ideally I'd like to have a standalone websocket service that handles long-running connections and then calls my specified API eg. `POST <my-http-service>/websocket/client/<client_id>`. Then the service can respond by sending a `POST <my-websocket-service>/websocket/client/<client>`, like an opensource https://pusher.com https://pusher.com? I realise it'd be fairly easy to build myself, just wondering if there is something off the shelf that achieves this?
- fasteo 5y ago
  Centrifugo maybe [1] [1] https://centrifugal.dev/ https://centrifugal.dev/
- ghughes 5y ago
  Have a look at Pushpin: https://pushpin.org/docs/about/ https://pushpin.org/docs/about/