looking what server. 64 arranges? (It at all is a lot of)
You want to tell that on one connection much ?
No more 10.
10 000 * = 600 it is a lot of 60 000 connections? If to compare with 64 ?
If everything that does this server, it on a web socket to send notification messages that the data changed, that clients did the ajax-inquiries quite arranges. Well and the elementary .
that you will be ?
If the information for the client is not present - the server does not work.
If the server does not work, information for the client never will be.
at ajax the client should request permanently.
It is not necessary to me to interrogate. For this purpose there is a web socket. And I will request/send the data on ajax. Also I will receive the maximum scoring on all fronts.
. the server should answer even if for the client there is no . not a big loading, but at a considerable quantity of clients the server should process requests permanently. Therefore scaling also is required.
Scaling is required not therefore. The overwhelming number of tasks, does not demand back coupling from the server. The data is necessary only when the user makes certain actions. Presses the button, receives result. So all web is arranged, and not only the web, too UI in itself does not live in a desktop, sits you wait for events from the user, or from trees yesterday tears?
And for notification messages, it is possible to use a web socket, it for this purpose and is created. Well even for games well.