Expand my Community achievements bar.

Learn about Edge Delivery Services in upcoming GEM session
SOLVED

Room Cleanup

Avatar

Level 2

We are developing a game service, and we create a room for our players to collaborate in while they are playing.  Each instance of a game (there are a lot of them) is assigned a unique room for the players to communicate in order to keep.  Once the game is complete, the room is no longer needed.

My question(s) are ones about the "tax" on your side of keeping these ghost rooms around.

- Do you guys clear out rooms that have not been used for a period of time?

- Is it a burden on your system for us not to clean them up? (i.e. do a server to server connection using your REST API to delete them)

- If needed, What would be your preferred approach for us to deal with these rooms that are no longer needed?

Thanks,

Steve

1 Accepted Solution

Avatar

Correct answer by
Former Community Member

Hi Steve,

Good questions -

- We don't clear your rooms (you might want them!).

- Eventually, yes, it is a burden (it's space in our database).

- If it's no longer needed, have your servers call ours and use the REST API to delete the ones you don't need. Either as users are leaving the room, or once a night/week or so.

nigel

View solution in original post

2 Replies

Avatar

Correct answer by
Former Community Member

Hi Steve,

Good questions -

- We don't clear your rooms (you might want them!).

- Eventually, yes, it is a burden (it's space in our database).

- If it's no longer needed, have your servers call ours and use the REST API to delete the ones you don't need. Either as users are leaving the room, or once a night/week or so.

nigel

Avatar

Level 2

Sounds like we'll clean them up, thanks Nigel!

The following has evaluated to null or missing: ==> liqladmin("SELECT id, value FROM metrics WHERE id = 'net_accepted_solutions' and user.id = '${acceptedAnswer.author.id}'").data.items [in template "analytics-container" at line 83, column 41] ---- Tip: It's the step after the last dot that caused this error, not those before it. ---- Tip: If the failing expression is known to be legally refer to something that's sometimes null or missing, either specify a default value like myOptionalVar!myDefault, or use <#if myOptionalVar??>when-present<#else>when-missing. (These only cover the last step of the expression; to cover the whole expression, use parenthesis: (myOptionalVar.foo)!myDefault, (myOptionalVar.foo)?? ---- ---- FTL stack trace ("~" means nesting-related): - Failed at: #assign answerAuthorNetSolutions = li... [in template "analytics-container" at line 83, column 5] ----