Yes Paul, exactly. There is a lobby browser and I would like to avoid polling it. I currently poll using lobbyProxy.getLobbyInstances to get the list, but then I have to loop through the list and get the settings/extra json with lobbyProxy.getLobbyData. However, all this is very expensive (1 API call getLobbyInstance and 1 API call for each getLobbyData). Having the created/deleted events would be ideal, alternatively if getLobbyInstances also returned the lobby settings it could also be an acceptable alternative.
There is also another problem: since the update is timed, closed lobbies are still visible to users in the browser, and this also creates a bit of confusion because at that point users have to be told that that lobby no longer exists if they click on it.
Greg, by connected users, I mean the users who are currently playing and are connected via RTT, regardless of whether they are in the lobby or not. It would be useful to have the possibility of sending a broadcast message to all players online at that moment or to a subset of users with some filter (e.g. he is playing a match, exclude him from the list).
Suggestions?
Thanks!