Photon Realtime Cache Write Ordering Boundary
0 reputation · 02 Aug 2021, 23:31 UTC
0 reputation · 02 Aug 2021, 23:31 UTC
The server maintains a shared global room cache for events.
Concurrent RaiseEvent calls from multiple clients interact via this shared state.
What is the documented boundary for which sender can mutate the global room cache?
35275 reputation · 03 Aug 2021, 11:24 UTC
The server maintains the authoritative global room cache. Concurrent RaiseEvent calls from multiple clients do not mutate the cache directly; they trigger server-side processing that dictates the write order.
Photon Realtime guarantees ordering through its internal server logic, not by enforcing a single master client. The server serializes or orders these events based on its internal processing pipeline (e.g., arrival time or application logic), ensuring a consistent state for all connected clients.
RaiseEvent calls from several clients and verify the resulting cache state sequence against expected ordering.To refine the answer, is the specific Photon Realtime server implementation running a custom event handler or relying solely on the default framework behavior?
Use comments to ask for clarification. Post a solution as an answer.
No question comments on this page.