Fixed - Created tables do not disappear when the player closes the browser.

This commit is contained in:
marcins78@gmail.com
2011-09-18 11:03:56 +00:00
parent 0b6611a0d3
commit 531fe20b79
2 changed files with 5 additions and 2 deletions

View File

@@ -21,7 +21,7 @@ public class HallServer extends AbstractServer {
private Map<String, LotroFormat> _supportedFormats = new HashMap<String, LotroFormat>();
private Map<String, AwaitingTable> _awaitingTables = new ConcurrentHashMap<String, AwaitingTable>();
private Map<String, String> _runningTables = Collections.synchronizedMap(new LinkedHashMap<String, String>());
private Map<String, String> _runningTables = new ConcurrentHashMap<String, String>();
private int _nextTableId = 1;
private final int _playerInactivityPeriod = 1000 * 10; // 10 seconds
@@ -128,6 +128,7 @@ public class HallServer extends AbstractServer {
}
public void processTables(String participantId, HallInfoVisitor visitor) {
_lastVisitedPlayers.put(participantId, System.currentTimeMillis());
visitor.playerIsWaiting(isPlayerWaiting(participantId));
Map<String, AwaitingTable> copy = new HashMap<String, AwaitingTable>(_awaitingTables);

View File

@@ -20,7 +20,8 @@ Optional:
4. Modify the Blueprint hierarchy to return possible return objects (PlayEventAction), TriggeredAction, etc. Use
final methods were possible to avoid implementation errors on new cards added.
10. Add active/all cards switch to the user interface.
32.
33. When a player stops responding during preparation time of the game, the game is not properly finished.
34.
DONE:
1. Introduce AbstractPermanent into Blueprint hierarchy.
@@ -46,3 +47,4 @@ with Filters.sameCard(...) filter.
27. Show list of players in the hall.
28. Introduce deck validation for FotR block format.
29. Player registration and login.
32. Created tables do not disappear when the player closes the browser.