Phoenix presence across topics

twinfire

I am beginning to look at phoenix presence and have some questions about the best way to achieve cross topic presence. My current design has every user having their own topic “user:xyz” and they can connect from many different clients (desktop, mobile1, mobile2, etc). Each user needs to be able to know of the presence of all the other users presence (client xyz should get presence updates for client abc, etc). Do I need to have an user:all topic that each user joins in addition to their user:xyz topic? I apologize if I am missing something but I figured somebody could point me in the right direction.

Thanks.

6 comments

/phoenix #presence

0 2710 6

2017-05-12 14:25:19 UTC

Showing Posts 1 to 6

Show Best Posts
Show All (oldest first)
Show All (newest first)

OvermindDL1

Exactly yes!

Post #1

twinfire

Ok, thanks. Can I auto join the users to the all topic when they join their user topic?

Post #2

OvermindDL1

Yep, just in an, say, after_join callback in the topic just put something kind of like:

Presence.track(self(), "user:all", blah_meta)
Presence.list("user:all")

The Presence.list/2 call can take the socket or the topic, and the only thing it does with the socket is grab the topic anyway as seen at:

github.com/phoenixframework/phoenix

lib/phoenix/presence.ex

v1.2.3


      
          
          def update(%Phoenix.Socket{} = socket, key, meta) do
            update(socket.channel_pid, socket.topic, key, meta)
          end
          def update(pid, topic, key, meta) do
            Phoenix.Tracker.update(__MODULE__, pid, topic, key, meta)
          end
          
          def fetch(_topic, presences), do: presences
          
          def list(%Phoenix.Socket{topic: topic}), do: list(topic)
          def list(topic) do
            Phoenix.Presence.list(__MODULE__, topic)
          end
          
          def handle_diff(diff, state) do
            Phoenix.Presence.handle_diff(__MODULE__,
              diff, state.node_name, state.pubsub_server, state.task_sup
            )
            {:ok, state}
          end

And Presence.track/3, the one that takes a socket, just delegates to Presence.track/4 by taking out the pic and topic anyway, so you can pass in whatever pid and topic you want (from within your topic use pid self()) as can be seen at:

github.com/phoenixframework/phoenix

lib/phoenix/presence.ex

v1.2.3


      
          def track(%Phoenix.Socket{} = socket, key, meta) do
            track(socket.channel_pid, socket.topic, key, meta)
          end

Post #3

twinfire

Thanks for the response!

Post #4

twinfire

Do I need to call Presence.track and Presence.list for both the user:xyz and the user:all topics in the same after_join?

Post #5

OvermindDL1

If you want them all then you need to track and list them all. Do note, if you have multiple presence’s tracking at the same time then Phoenix does not have a client-side way of differentiating them since they all go to the same message event name (really wish that were configurable at track time). You can fix that by overriding the presence_diff event as an outgoing type message and re-route each type to their own event names.

Post #6

— All posts loaded —