That is just automated client polling.
No it is not, actually. The scripting is used to create some kind of "client site server" that connects to the web server and waits for events on the connection. The web server is that pushes events on the connection. The client side script reacts on these events and changes the document accordingly.
The HTTP protocol fully supports persistent connections with the keep-alive header. But that is not the problem. The problem here is that you want to have
active content. Browsers don't support active content well because they are for browsing
IMO anything active should be using a different setup and not bolted into a browser. A browser is poorly suited to active tasks; as is evidenced by the multitudes of exploits and the poor performance of scripting. And now it seems google feel they have the right to run native code in people's boxes? What could possibly go wrong?
Index
> Main > Anybody managed to make an NaCl demo in fasm?
07 May 2014, 09:44