mnkhod
Just finished reading about Phoenix Channels and now im confused on how i can use channels with LiveView to sync my page with everyone who is using the page.
Quick Trip with AI is telling me to use PubSub. When i try to check out the LiveView Hex Docs for guidance on how to use pubsub or channels with LiveView, i couldnt find any material on it.
I just wanted to learn more about the combined usage and its best practices, let me know if both usage is fine but i still wanna know what the community best practice and use case on when to use channels and when to use PubSub with LV.
Thanks in advance
Trending in Questions
Hey guys,
I’ve got a huge CSV ( around 10 GB ) that needs to be processed hourly
Do you guys have any suggestions what is the best prac...
New
I’m working on a project that simulates the bumbl example in the programming phoenix book. It acts almost like an email client. We have a...
New
Hello!
Could someone please give me a help/sample code, how to delete a file from s3 using waffle/waffle_ecto from Phoenix app.
I creat...
New
I’m seeing that a list inside a Kino.DataTable will be interpreted as a charlist, even if the Kino.configure() is set to charlists: :as_l...
New
So my question is quite simple and i have found no conclusive answer on forum, google or AI.
Should we use :erlang.float for Integer to ...
New
Hi, I’ve just set up an application with ash_authentication. There is only magic link strategy for now, so there is no confirmation add o...
New
If a change or preparation module uses Ash.Changeset.get_argument/2 or Ash.Query.get_argument/2 (or any of the other get_argument functio...
New
Other Trending Topics
I am happy to introduce the very α version of the new programming language compiled to BEAM.
Welcome Cure.
It has literally three kille...
New
Hobbes is a low-level distributed database for the Elixir programming language.
Hobbes provides a simple, safe, and scalable storage lay...
New
Hi there! We created Gust: A task orchestrator inspired by Airflow.
For those who have never heard about Aiflow, it’s a Python-based wor...
New
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
Hello everyone. After busy few months I am happy to announce v0.1.0 of Emerge & Solve.
They are GUI (Emerge) and State management (S...
New
Corex is an accessible, unstyled UI component library for Phoenix that integrates Zag.js state machines using Vanilla JavaScript and Live...
New
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
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #blog-post
- #elixirconf-us
- #elixir-ls
- #ai
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #hex
- #security
- #metaprogramming











Showing Posts 1 to 7- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
LostKobrakai
You might want to look at Matrjoschka of phoenix communication | Benjamin Milde. It should make the distinction between the tools more clear. Generally the question will be why you need channels – not just PubSub – when you already have LV running (on top of channels).
manhvu
Another case for using Phoenix PubSub in a cluster (with src demo) for you Using Phoenix.PubSub as a message-bus for Elixir cluster
namxam
I guess you are quite new to elixir and phoenix. So I will try my best - I am not good at explaining
The LiveView model allows live communication between the server and the client browser. But each user is served its own instance of the LiveView. So they do not know of each other.
The PubSub part allows you to send the same message to all subscribers, so you can notify them about changes.
In your case, you would subscribe to a specific PubSub message from the LiveView. And in the LiveView you handle the PubSub message.
You could, for example, broadcast a {:content_updated, 134} message. And the LiveView then knows, that it has to reload the data for that id.
Not full example, but perhaps to explain the difference between the concepts.
jam
Namxam has it right. The only thing I’d add to answer your original question is: if you’re using LiveView you can ignore the Channel documentation. Just focus on LiveView and PubSub. Channels are useful when you’re not using LiveView, e.g. you have a separate frontend.
codeanpeace
And that’s because
Phoenix.LiveView.Channelbuilds on top ofPhoenix.Channelwhich is why you might not need to interact with Channels directly when you are already using LiveViewthiagomajesk
Sometime ago, I published a blog post about how I built a turn-based battle game prototype, which uses PubSub to push state to multiple clients/players. If you are into gaming, the theme might ease you into my poor didactics
.
You can check the post here: How I created a JRPG battler with Elixir - the code is also open source if you want to follow along.
lubien
This is my go to reference on understanding pubsub for the first time!