ream88
When mounting my live view, I register it as a participant in a running GenServer.
def mount(_params, _session, socket) do
MyGenServer.add_participant(self())
{:ok, socket}
end
This allows me to easily work with a list of participants very easily. I now introduced some JS dependency which creates a unique ID for each participant/rendered live view and pushes it back to the server, which stores it in its assigns. However for my app to properly work, I would need a list of these unique IDs across all my participants. This can be done via :sys.gen_state, but feels very wrong.
MyGenServer.participants()
|> Enum.map(fn participant →
:sys.gen_state(participant)
|> Map.get(:socket)
|> Map.get(:assigns)
end)
Is there an official way to get assigns from a live-view process from outside of the process?
Trending in Questions
Hello!
Suppose you are building workflow (order / task / payment) processing system with the following requirements:
Each workflow con...
New
I’m aware of 2 such projects, are there others?
git: GitHub - team-alembic/realworld: A fullstack Phoenix LiveView application with back...
New
I having some trouble figuring out if I have set myself too strict of standards for my production server. Currently I can handle 75% of r...
New
Hi everyone.
My team and I have been working on a fairly modest app based around video streaming and chat, but we’ve landed a customer t...
New
I really like the adapter patterns that ecto, nebulex, waffle, etc. use and would love find something similar for a key management servic...
New
Hello folks!
So at work, we are seeing some situations where we have to define some “fixed” strings that are used across the codebase in...
New
How Can I Optimise Compile Time Dependencies
I have been building an elixir application for about 2 years now. Many modules and files ha...
New
Other Trending Topics
I fully migrated to my own harness from Anthropic/Gemini and I think it’s time to share it. Welcome DSH, the DeepSeek Harness, fully writ...
New
Hey. Is there anyone here who creates agents in their apps? Not talking about using agents, but creating them. I’m finding it pretty diff...
New
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
There has been a thread to discuss the Stack Overflow Developer Survey on this forum every year since 2018, so here’s yet another one for...
New
I love Elixir. It’s one of 2 programming languages I’ve ever fallen in love with.
But I don’t use it anymore.
Serverless was the promis...
New
Emily is an Elixir library that runs Nx computations on Apple’s MLX. Install it as the default Nx backend and Nx, defn, Axon, Nx.Serving,...
New
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #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
- #ai
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #blog-post
- #elixirconf-us
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #elixirconf-eu
- #api
- #forms
- #security
- #hex










Showing Posts 1 to 3- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
benwilson512
I wouldn’t really recommend thinking this way. Assigns belong to the socket. What do you need them for in the genserver?
ream88
I need a way to share the assigns across all my live views. Each live view gets a unique ID, and the other live views connected to the server should see this unique ID. (I need this ID to connect all users to a video channel.)
benwilson512
I would consider using something like Registry so that each live view could register its unique ID.
This sounds like an XY problem. Each live view is a different process, process state isn’t really shareable. You can message it around, but it’s gonna get copied each time and isn’t going to stay up to date as the process state changes. It’s fine to message around the ID, but I wouldn’t do so for the full assigns. Can you elaborate on what you’re trying to do more?