Websocketd – It's like CGI, twenty years later, for WebSockets

Re:Websocketd – It's like CGI, twenty years later, for WebSo... by fasteo on Thursday December 23, 2021 @03:47AM (#29659949)

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

[ Parent | on HN ]

Re:Websocketd – It's like CGI, twenty years later, for WebSo... by cloudyglider on Thursday December 23, 2021 @05:48AM (#29660586)

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? I realise it'd be fairly easy to build myself, just wondering if there is something off the shelf that achieves this?

[ Parent | on HN ]

Re:Websocketd – It's like CGI, twenty years later, for WebSo... by fasteo on Thursday December 23, 2021 @06:09AM (#29660702)

Centrifugo maybe [1]

[1] https://centrifugal.dev/

[ Parent | on HN ]

Re:Websocketd – It's like CGI, twenty years later, for WebSo... by ghughes on Thursday December 23, 2021 @08:22AM (#29661574)

Have a look at Pushpin: https://pushpin.org/docs/about/

[ Parent | on HN ]