ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Goal Determine how the documented 500 messages/second per‑room guideline in Photon Realtime 4.0 influences latency when many peers send events concurrently, and identify whether this behavior is consistent across Photon Cloud and self‑hosted Server deployments. Constraints & Uncertainty The 500 msg/s figure is documented as guidance; the actual server ma
Photon Realtime employs a Concurrent User (CCU) licensing model where costs are tied to peak simultaneous connections. In low-traffic environments, maintaining an accurate CCU count is critical to staying within the limits of the Free or low-tier subscriptions and avoiding connection rejections. There is a technical distinction between a graceful shutdown an
Goal: Determine whether developers should manually clean up unused interest groups in Photon Realtime or rely on custom properties for event filtering. Constraints: Interest group subscriptions are not persisted across reconnections, the server supports a maximum of 255 groups per client, and there is no built‑in mechanism to automatically remove unused grou
When integrating Unity with Photon Realtime, developers must choose between the high-level PhotonView ObservedComponents for state synchronization and the lower-level RaiseEvent method for custom data transmission. The goal is to maintain consistent game state across clients while minimizing network congestion. While ObservedComponents automate property sync
Developers using Photon Realtime need to decide how to handle the room list cache that does not automatically expire entries based on time. The cache is refreshed only when the client calls OpGetRoomList or when the server pushes updates according to the lobby’s update interval, which can leave closed or full rooms visible longer than desired. The goal is to
Event Deduplication in Reliable UDP Photon Realtime utilizes a reliable UDP layer to ensure packets are delivered in order. While the transport layer handles re-transmissions, application-level retry logic is often implemented to ensure critical state changes are acknowledged by the receiver. A challenge arises when using RaiseEvent with reliable delivery. I
Photon Realtime Event Caching The server maintains a shared global room cache for events. Concurrency Constraint 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? How is the server guaranteed to order concurrent cache write operations from diffe
I'm planning a zero-downtime migration for a small realtime app on Photon Engine. The current plan is to keep one Photon Cloud App ID so old and new client builds share the same rooms, and rely on PlayerTTL/EmptyRoomTTL plus rejoin with the same user ID so disconnected players resume their actor slot instead of re-entering as new actors. The uncertainty is t
photonengine