| 1 |
It's n^2 thing.
|
1 |
It's n^2 thing.
|
| 2 |
Each visible player also means updates about ingame status and about battles they are in etc.
|
2 |
Each visible player also means updates about ingame status and about battles they are in etc.
|
| 3 |
\n
|
3 |
\n
|
| 4 |
Now imagine 30 people game ending and 1000 people online. If those 30 people are visible to all, you have to send 30 000 messages just for the "battle ends" event.
|
4 |
Now imagine 30 people game ending and 1000 people online. If those 30 people are visible to all, you have to send 30 000 messages just for the "battle ends" event.
|
| 5 |
\n
|
5 |
\n
|
|
|
6 |
\n
|
|
|
7 |
Now imagine server restarts and 1000 people join at once.
|
|
|
8 |
Suddenly you are sending many multiplies of 1000x1000 custom messages as they open/join games, join chat channels etc.
|
|
|
9 |
All of these have to be serialized and pushed over network.
|
Can someone explain how the player list works?