Closed Bug 1074700 Opened 10 years ago Closed 10 years ago

[meta] As a user, I don't want my active rooms to expire

Categories

(Hello (Loop) :: Client, enhancement, P1)

Product:
Hello (Loop)
Component:
Client
Type:
enhancement

Tracking

(Not tracked)

Status:
RESOLVED FIXED
Blocking Flags:
backlog -

People

(Reporter: standard8, Unassigned)

References

Details

(Whiteboard: [rooms])

User Story

As a user, I don't want my active rooms to expire

UX:
* Reset the expiration date when there is "activity" in the room

Implementation:
* When a room is entered, PATCH the room, to refresh the expiry to 8 weeks
No description provided.
User Story: (updated)
Blocks: 1076413
Moving discussion from bug 1076413 comment 3: (In reply to Alexis Metaireau (:alexis) from comment #3) > The wiki page about the rooms feature [0] says the rooms should expire after > a certain amount of time that's defined by the room creator. > > The server implementation we have is currently expiring them, as defined in > the document. We need product to make a decision here about this, and can > update the code accordingly then. > > [0] https://wiki.mozilla.org/Loop/Architecture/Rooms#POST_.2Frooms Product has already made the decision - please see the user story for this bug. My original expectation is that the client will inform the server when there's activity in the room. However, it could be more appropriate for the server to update the activity. The full spec from product is: - When the room gets activity reset the timer - Silently remove rooms from list upon expiration - Definition of activity: 1) Someone joined the room, 2) share the room URL 3) copied the room URL From the way I see this, 1) could be either server or client, and 2 and 3 would need to be client. Thoughts?
Yes, this could be done on the server side for 1), since we know when someone joins / quit / etc, and we're actually already refreshing some other date. It's already possible to update the expiration time from the client (if the client is the room owner).
backlog: --- → Fx35+
Priority: -- → P1
Depends on: 1100556
Depends on: 1100558
I've split this into two bugs - the simple update on join is a server bug (bug 1100556) and simple to implement; the update on copy/email is probably server and client, but covered in bug 1100558, and slightly more complex due to api changes.
backlog: Fx35+ → ---
Summary: As a user, I don't want my active rooms to expire → [meta] As a user, I don't want my active rooms to expire
backlog: --- → -
Marking resolved fixed because we have a solution for shipment. Bug 1100558 will be done as a follow on enhancement, currently targeting Fx37.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.