FMSGuru

Hello!

What's the best way to keep a List of an Application connected Users in the Server that every Client can see (maybe with restricted levels) and keep updated all the time? For instance, if a User connects/disconnects, the list would be updated and sent to all other Client.

I have tried using SO (passing the Users array in the Server) but I was not satisfied with the solution I did.
So, then I created an object in the server (the way you did in your last tutorial) and am taking profit of SO to use its Broadcasting features (onSync). Once the Client receives SO notification that something has changed in the list, each client sends a Server request to receive the updated list (NetConnection.call with receiving method).

Is this too much work for the server? Is this too slow? I estimate each List may contain 100/200 Users (ID, nick, gender, nationality, and a few other info) and there should be not more than 100 active lists (each user may connect to let's say, 10 lists at most)

Although it looks it will work fine (I still am working on it), I am not satisfied yet, so, I would like to hear your great ideas/suggestions.

Best regards and thank you for your time, your interest and your hard work.
Lautaro

I would keep track of the users on the server, when a client connects up then give them the list. Any updates after that should just be the changed info, not the whole list. That should work well. Your technique for doing that should work just fine too.

Thanks Graeme.

Good to hear the schema I was doing is not an aberration.

It has started to work and it looks its performance is soooo good; my Client and me, we are really impressed.

Although, it is easy to recognize your approach is better than mine because it will use less bandwidth and process would be faster (more coding but faster running). As soon as I finish this first stage I'll work in your suggestion.

Thanks for yor help and interest.

Lautaro.