Basics of geckos.io

[julifos]

I have a basic understanding on multiplayer games and I developed my own before using Smartfox Server. Here comes the questions: What is a "channel"? What is a "room"? Can I create channels and rooms?
I'm used to habe a lobby (ie, connected users waiting to join zones/rooms), zones and rooms which you can create statically (ie, a chat room which admits a max. of 100 users) or dynamically (ie, you can create a room and let enter 4 players in order to play a game, and afterwards destroy such room).
Also, what are the limits? (number of concurrent users, memory, garbage collection and so on)
Thanks in advance for any hints or guidance (or links to more info!).

[julifos]

Trying to auto-answer before someone else with the knowledge does, with the hope that I will be corrected or this info will make happy someone in a future. I've been going thru the source and making some tests and seems that:

• io: instance of the server, hosts any number of incoming connections.
• channel: user. The array of connected users exists on the channel's webrtcConnection property (connections) or in the io.connectionsManager.
• room: looks like a regular room. You invent the room, ie room 54 or room "tango", and you join the user inside, then you can send messages in that particular room. So, creating a room is a simple channel.join('sugar'). I think this could be improved, so every geckos.io user doesn't reinvent the wheel every time (ie, writing some kind of room manager which tracks all the existing rooms with its own properties and logics, etc.).

So, messages can be delivered like this:
channel.emit('event-label-or-invent','Only myself receive this message')
io.emit('event-label-or-invent','Everyone receives this message')
channel.room.emit('event-label-or-invent','Only people in my room receives this message')
io.room('roomba').emit('event-label-or-invent','Only users in the room "roomba" receive this message')
channel.broadcast.emit('event-label-or-invent', 'Everyone in my room except myself receives this message')

Not sure if you can send a message only to a specific user, this would be a very interesting feature request (ie, admin purposes, personal messages, etc.). And some more admin capabilities. I think you can "kick" users accessing the _ connectionsManager_ and maybe implement ban or similar functions yourself.