Feature #58

Room Specific Client Timeout

Added by derek clayton 1348 days ago. Updated 884 days ago.

Status :Closed Start :09/09/2008
Priority :Normal Due date :
Assigned to :derek clayton % Done :

0%
Category :Rooms
Target version :Union Server 1.0 Alpha 6

Description

  • Add the ability to set a Client Timeout specific to a Room which overrides the Server setting.

Decide what constitutes client activity.

  • Currently, messages sent to a room (i.e., u1 UPCs) go through the "u" room, which unintuitively means that sending a message to room "foo" is not considered activity for room "foo".
  • Workaround 1: heartbeat the room with a custom UPC.
  • Workaround 2: Use a server-wide timeout.
  • Two agendas: ghost detection versus application loitering (i.e., a client is disconnected without the server's knowledge versus a game that wants to kick a player that's not playing)

History

09/13/2008 11:09 PM - colin moock

  • Category set to Rooms

07/18/2009 04:07 PM - derek clayton

  • Priority changed from High to Normal
  • Target version set to Pending Review

12/10/2009 10:18 AM - derek clayton

  • Status changed from New to Closed

This todo is based on the old architecture. Messages no longer use the "u" room.

12/17/2009 12:56 AM - derek clayton

  • Target version changed from Pending Review to Union Server 1.0 Alpha 6

Also available in: Atom