This change isn't even listed in the changelog, but fatal:
io.sockets.adapter.rooms[<room name>] seems to be an Object of type Room now, having a the list of its sockets in an property "sockets".
Before version 1.4.0, the map of sockets was directly accessable by the call (there was no Room object)...

Moved logic for iterating the room's sockets to a new method _iterateEachJoinedSocket() though. So future changes to the API (which are very likely) can be modified on one place in the code...

Socket.io likes to break API on minor versions, grml!
Cannot think of what they would do on major versions...

Since version 1.9.1 the watch task crashes by an error, when changing a file... strange :-/

* Refactored the class again to use weights instead of sizes for rating entries
* Simplified sub routines to be more efficient
* Initializing helper object and doing checks in client event listeners

TODO: Move settings for flooding protection to config

* Always show number of players
* Hide players list, if it is empty, allow overwrite by using css class "secret"
* Have four "formSection" containers in server tab
* Added css class for tab pages
* Tab title/channel name is now contained in span tag
* Tab headers having tooltips showing the channel name

Note:
Because translations are set to DOM in escaped form, the texts have to be decoded before.

On disconnect, sockets are in no rooms anymore - even before kicking them out manually.
Because of that, removeClient() did cancel in beginning...
But anaway, we have to remove the client from the unique users list - so force it.

This will temporary leave the channel...

TODO:
- Button for temporary leaving custom channels (Leave with param true)
- Flooding protection!
-- Add closure to client socket, which handles counting emits (By SocketHandler)
-- All client event handlers must call counting method of closure
-- Disconnect client on threshold overflow...

Not finished yet...

TODO:
- Button for temporary leaving custom channels (Leave with param true)
- Disallow permanent leaving of self-created channels (and non-custom channels)
- Deletion of self-created channels
- Response messages after leaving/deleting channels

Also added some client side flood protection to reduce delay effect of irc flood protection...

TODO:
- Webclient: Extend gui for channel creation (What is optional when joining?)
- Temporary leaving custom channels (Without DB update)
- Permanent leaving custom channels (With DB update)

- Flooding protection!
-- Add closure to client socket, which handles counting emits (By SocketHandler)
-- All client event handlers must call counting method of closure
-- Disconnect client on threshold overflow...

- New column CreatorUserID for channel table
- Refactored channel join handler: Validate data on beginning, moved sub routines to methods

TODO:
- Check channel limit (server side)
- Translations for server messages
- Webclient: Extend gui for channel creation (What is optional when joining?)
- Temporary leaving custom channels (Without DB update)
- Permanent leaving custom channels (With DB update)

- Flooding protection!
-- Add closure to client socket, which handles counting emits (By SocketHandler)
-- All client event handlers must call counting method of closure
-- Disconnect client on threshold overflow...