Photon Realtime Room List Cache Expiration Configuration

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 establish a clear policy for cache freshness that balances matchmaking reliability against server bandwidth usage.

Uncertainty remains about whether a client‑side TTL should be applied to room list entries, what TTL value is appropriate, and how it interacts with the server‑provided lobby statistics and update interval.

• What maximum staleness is acceptable for room list data in matchmaking scenarios?
• Should developers implement a client‑side TTL for cached room list entries, and if so, what TTL range minimizes stale matches without excessive bandwidth?
• How does adjusting the lobby’s update interval affect the effectiveness of a client‑side TTL?