cedric
Actioncable - like in Rails, but for Elixir
Hi,
I just published an equivalent of actioncable (same as Rails) in elixir, this is a first version but it works. Here it is : GitHub - cedricPoncot/actioncable: Actioncable implementation (server-side) like in Rails, but in Elixir. · GitHub
Feel free to make some feedback ![]()
Most Liked
kokolegorille
I am curious why You don’t use Phoenix channels instead.
The use of Redis might be required for Rails, but maybe it’s less useful in Elixir ![]()
cedric
It’s the point
, if you switch your server from Rails to Elixir, you don’t have to change existing JS code on client.
cedric
Hi
,
I’ve tried with Phoenix Channels first.
The problem is : to be compatible with action cable protocol, specially during 101 Switching protocol Phoenix Channel wasn’t offering enough flexibility. That’s why i use something more low level : Cowboy websocket handler.
For Redis, you’re absolutely right, this is not necessary. It was just easier to implement with ![]()
(The purpose of redis in this package is only to store list of pid corresponding to a channel)
Popular in Announcing
Other popular topics
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #deployment
- #library
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #channels
- #elixirconf
- #exunit
- #discussion
- #code-sync
- #javascript
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixir-ls
- #phoenix_html
- #iex
- #blog-post
- #graphql
- #genstage
- #ai
- #websockets
- #supervisor
- #advent-of-code
- #elixirconf-us
- #distillery
- #processes
- #forms
- #api
- #metaprogramming
- #security
- #performance








