- Now with websockets!

A few months back, I had added support for web sockets in, up until now it's only been used for noVNC, the all-Javascript VNC client and nothing else. Web sockets allow for full two-way communication between the server and the web browser for almost all browsers except Internet Explorer (this will be fixed in IE10). Using web sockets instead of the emulated technique using a series of HTTP calls allows for better performance and much less overhead. I can also handle many more sessions on the server side.

Well, in the last few days, I have been attempting to make use of web sockets more broadly thru out the site. Yesterday I released a new version of the site that makes use of them, when the browser supports it, for the remote desktop and remote terminal. If you notice any issues, please post a comment below. In general it seems to work ok, I am still working out all the kinks.

Quick update: I had to back-off using web sockets on Safari browsers including iOS because web sockets seems to be crashing the browser. So, it's back to AJAX HTTP for Safari just like IE. Firefox and Chrome seem to be powering thru with web sockets.

Para obter informações mais completas sobre otimizações do compilador, consulte nosso aviso de otimização.