How to put something in a socket's assigns from another process

Looks like it yeah, that is how I’ve used it at least and it works.

So is it like a predefined verb in phoenix? I don’t have to write anything, just send “disconnect” event to a socket and it would disconnect?

The disconnect message is handled internally to the socket. If you want to handle when it disconnects then setup a normal OTP-style monitor, nothing special with that.

Sorry, but I still don’t understand how the example in the comments to id/1 function Test.Web.Endpoint.broadcast "user_socket:#{id}", "disconnect", %{} works.

Where if not in the UserSocket would I implement the disconnecting logic?

I thought that changing the assigns in the socket would change them everywhere, but as you said earlier, it was wrong since they are copied into channels. So yeah, there is little reason to receive messages in the socket.

Thanks.

Thought it might not, Sockets are for handling sockets only so that makes sense, keep it to channels then.

I’m not sure why you would want to receive messages in the socket to be honest, I’ve never thought up a need other than disconnecting them…

And it doesn’t seem to not conform to the genserver behaviour anywhere in the code phoenix/lib/phoenix/socket.ex at main · phoenixframework/phoenix · GitHub

If you are broadcasting to the topic set in your id method on the UserSocket, then you’d handle it in the UserSocket module itself if it allows you to override handle_info (I’m not sure it does for safety reasons, but I’ve not tried).

I’ve tried adding

  def handle_info(event, msg, socket) do
    IO.inspect([event, msg, socket])
    {:noreply, socket}
  end

  def handle_info(event, socket) do
    IO.inspect([event, socket])
    {:noreply, socket}
  end

to UserSocket module but still no IO.inspect got called.

You can sure, it just won’t do anything unless other broadcast messages use them. Remember that the channels get a ‘copy’ of the assigns, so changing it in the channel will do absolutely nothing to theirs.

Why is it not good for modifying the socket’s assigns?