nathanl
Is this how Phoenix.Channel and PubSub should interact?
I came across some interactions between Channels and PubSub yesterday which surprised me. This is using phoenix 1.7.1 and phoenix_pubsub 2.1.1.
If I have a Phoenix.Channel on topic "some_topic and a client connected to it:
Phoenix.PubSub.broadcast(MyApp.PubSub, "some_topic", %{some: "message"}will go to that channel process’shandle_info/2even if it did not callPhoenix.PubSub.subscribe/3, and will go N+1 times if it did explicitly subscribe N times.MyApp.Endpoint.broadcast("some_topic", "some_event", %{some: "message"})will go directly to the connected client of the channel without the channel process ever seeing it unless the channel process intercepts it.
Is this how it’s intended to work? My mental model was “only processes which explicitly PubSub.subscribe/3 will get a PubSub event, and it will go to their handle_info/2, where they can do what they will.” I see that handle_out/3 exists for interception, so clearly that’s by design…
I’ve been using Phoenix for years and didn’t realize that the topics were shared between Channels and PubSub. But I may not be the sharpest knife in the drawer. 
Most Liked
chrismccord
Yes this is working exactly it is supposed to 
Channel broadcasts (broacast(socket, ...) and Endpoint.broadcast )) are “fast-laned” directly to the transport process unless you intercept. This allows us to encode the the message a single time vs N times for every subscriber. Phoenix.PubSub.broadcast is lower level and broadcasts the raw elixir term as is, vs channel broadcast where it is wrapped internally in a Phoenix.Socket.Broadcast struct. As far as your dup subscriptions go, it’s the subscribers job to avoid duplicate subscriptions as there is a performance cost in checking on the subscribe side. Hope that helps!
Last Post!
nathanl
Yes, with the difference that if I forget to intercept a particular message, it will go to the client, but if I forget to handle_info one, it will blow up and I’ll notice in development.
Popular in Questions
Other popular topics
Latest Phoenix Threads
Latest on Elixir Forum
Sponsor Spotlight
Catch errors, track performance, monitor hosts and more.
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
- #elixirconf-us
- #advent-of-code
- #distillery
- #processes
- #forms
- #api
- #metaprogramming
- #hex
- #security
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
Error tracking for Elixir devs who love to ship. Start your free account.
Practical resources that improve the lives of professional developers.
Develop your skills with books, videos, and courses.
Enabling companies to succeed by building software people love.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"