News for hackers. Stuff that matters.

A comment on Use Phoenix Channels. Parent comment

Re:Use Phoenix Channels by jkarneges on Wednesday August 04, 2021 @11:36AM (#28062238)
> just drop it in

Have you looked at Pushpin [1]? (disclosure: I'm the lead dev). The goal is to be able to add it to anything, rather than requiring a certain language.

[1] https://github.com/fanout/pushpin

[ Parent | on HN ]
Re:Use Phoenix Channels by aloukissas on Wednesday August 04, 2021 @12:20PM (#28062841)
I haven't, thanks for the pointer! However, the main reason I chose Elixir/Phoenix for this project was not for the language itself, but for the runtime/VM (BEAM), which is battle-tested for such use cases.
[ Parent | on HN ]
Re:Use Phoenix Channels by ch4s3 on Wednesday August 04, 2021 @12:14PM (#28062755)
This seem pretty nice. How does it handle things like websocket reconnection?
[ Parent | on HN ]
Re:Use Phoenix Channels by jkarneges on Wednesday August 04, 2021 @12:48PM (#28063244)
Whenever a client connects (whether the first time, or on reconnect) or sends a message, Pushpin sends an HTTP request to a configured backend to retrieve WebSocket messages to be delivered to the client. This can be used to restore state on reconnect.

If you mean how is reconnection handled on the client side, that's up to the client. Pushpin is a server-side component with no client library. But the client could use a WebSocket library with reconnection ability, like reconnecting-websocket.

[ Parent | on HN ]