Maybe you can use something like this: GitHub - lyokato/riverside: Elixir Library: Simple WebSocket Server Framework · GitHub ( Riverside - Plain WebSocket Server Framework for Elixir)
dmarko484
chrismccord
Creator of Phoenix
@LostKobrakai covered the details perfectly here in how channels work and what’s required. Any client can talk to channels if they can write bits on the wire, and elixir clients exist in the community. Here’s a great one that you can drop in and work with:
7
entone
I’ve successfully built a 3rd party API on top of Phoenix channels. There are a few implementations in other languages that you can see here, Channels — Phoenix v1.8.8
In addition I built a Javascript library that wraps the JS Phoenix channels client to provide a more succinct API to our backend, https://www.npmjs.com/package/frontline-client
2
TwistingTwists
I use phoenix channels as back-end api to call on angular frontend.
You can do one of the following after npm i phoenix
-
put the
user-socket.jsfile in your angular (whatever frontend you consume api) -
import Socket from phoenix- for specific channel implementation
Let me know if this helps.
You can also get a hint of this from here.
Otherwise, i will try to extract a bare bones implementation.
1
TwistingTwists
If you can share the code where you are trying to implement phoenix channels, maybe it helps to debug.
What does join function look like in your case?
0
quda
@entone & @TwistingTwists thanks both but it was not what I was looking for: an agnostic implementation of ws with Phoenix channels. The channels architecture does not allow that, so I have to go at a lower level and build up from there: Plug cowboy → cowboy_websocket. I’ll tackle this another time though.
For the time being I already built a dirty quick solution for my needs on Node.
3