Bug #326

Account attribute update inconsistency.

Added by derek clayton 664 days ago. Updated 318 days ago.

Status :New Start :04/11/2010
Priority :Normal Due date :
Assigned to :derek clayton % Done :

0%
Category :Persistence
Target version :Future

Description

Client has a pre-existing room scoped account attribute.

Case 1:

Client connects.
Client logs in.
Client creates room and room doesn't exist.
Client observes room.

Client receives u8 and u54 containing the room scoped account attribute.

Case 2:

Client connects.
Client logs in.
Client creates room and room exists.
Client observes room.

Client receives u54 only containing the room scoped account attribute.

Case 3:

Client connects.
Client logs in.
Client creates room and room doesn't exist.
Client joins room.

Client receives u8 and u54 containing the room scoped account attribute.

THEN

Client disconnects.
Client connects again.
Client logs in.
Client creates room and room doesn't exist (because it was removed due to dieOnEmpty rules).
Client joins room.

Client receives u54 only containing the room scoped account attribute.

History

04/11/2010 05:49 PM - derek clayton

  • Status changed from New to Closed

04/11/2010 05:50 PM - derek clayton

  • Status changed from Closed to New

11/19/2010 10:05 PM - colin moock

  • Subject changed from When a logged-in client observes a room, its account attrs scoped to the room should be auto-loaded. to When a logged-in client observes a room, its account attrs scoped to the room should be auto-loaded

11/24/2010 07:12 PM - derek clayton

  • Subject changed from When a logged-in client observes a room, its account attrs scoped to the room should be auto-loaded to Account attribute updates for logged in observers.

01/19/2011 02:39 PM - derek clayton

  • Subject changed from Account attribute updates for logged in observers. to Account attribute update inconsistency.

03/22/2011 05:32 PM - derek clayton

  • Target version changed from Union 1.0 Beta 2 to Future

Also available in: Atom