fix: on new keys, disconnect user socket

[filipecabaco]

What kind of change does this PR introduce?

on new keys, disconnect user socket

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

1 Skipped Deployment

Name	Status	Preview	Comments	Updated (UTC)
realtime-demo	⬜️ Ignored (Inspect)	Visit Preview		Feb 12, 2025 9:51pm

[filipecabaco]

hey @supabase/dashbit 👋

we're looking for a way to:

• On triggering event we are able to kill all sockets and channels for a given tenant
• This event can be triggered from various sources
• A last message must be sent to all channels to inform users that they will be disconnected

with the approach of this PR (which I was unable to test properly the socket shutdown) we would potentially have two issues:

• Mailbox of process is full and we shutdown the socket later than we want
• Unable to send a last message to connected clients informing them that the channel will be shutdown

how could we go around this issue? my current potential approaches are:

• ETS table that has a tenant key and a list of socket pids which then we could use to broadcast the termination message and subsequently Process.kill the socket pid
• GenServer that would track similar information per socket and do the same flow
  ( basically either store in process or in ets 😅 )

Or would I be able to achieve the same using the socket "disconnect" event?

Thank you for your help.