Design C#MS custom event subscription logic

[cdhanna]

From a C#MS, customers want the ability to bind callbacks on custom beamable event names. These event names could come from the standard beamables one (like content.refresh), or developer created ones.

There are 3 types of events in general,

• player facing
• server facing
• "game" facing

This ticket is only supporting the server facing events. Player and Game events are about sending/receiving events between PLAYER accounts. The server side events are split into 2 sub groups

• game.one
• game.all

The .one events are events that are only handled by a single receiver, and the .all events are sent to all other game servers. This is where things get confusing for our design, because the subscription is not the place where the one/all is defined. That distinction happens at the emission of the event.

Also, because we have 10 connections per process, if you subscribe to an "all" event, do we actually want all 10 connections to get the event? But likely, we really want an "all" event to be handled ONCE PER PROCESS (but all processes)

[cdhanna]

we should gather some use cases from existing customers who have achieved this via workarounds.