brendonovich / eventsocket Goto Github PK

Depends on #3

Disable with SELF_HOST=true

Features behind paywall:

• #3
• #4
• #5

Instead of storing each socket connection in the DB, it makes more sense to store it in memory. The idea is to have a Horde DynamicSupervisor that watches a NodeListener and a bunch of processes (one per user) that contain data about each user's connected sockets. These processes will be referenced by a Horde Registry that maps user ids to their respective process and will restart as needed by Horde on new machines when necessary, preserving their state.

Things to consider:

• Does the 10 second grace period for websocket disconnects affect Horde's process distribution? I don't think so since the DynamicSupervisor will be a sibling of the endpoint, thus it should be able handle exit trapping on its own.