server-push

Which one's better: Socket.IO or SockJS and what are the biggest differences? How difficult is it to rebuild a completely ajax based page into a node.JS / socket.io based page? Do I have to recode absolutely everything? Are there any good tutorials on how to do this? Is it worth to do it (in your opinion)? SockJS has more server-side options available. If you don't want to be tied to Node.js, then it may be an option. The scaling seems to work best, from some benchmarks using PyPy to host the server-side portion. socket.io has more transport options, which include Flash. Even if you don't like

My ASP.NET MVC 4 Web application is displaying frequently updated data to the client. Data originate from an external source (an application installed on the server) and processed by SQL Server 2008 R2. Currently the data flow is quite traditional: clients polls from ASP.NET, ASP.NET polls in its turn from SQL Server. To avoid polling (and now that I require a real-time interaction between the users of the Web Application), I am changing the approach to push, using signalR to broadcast data to clients. This increases the smoothness of the user experience and also reduces the overhead of

I'd like to build a multiplayer web game application in which it supports chat. I presume the application will have to handle hundreds of simultaneous connections. I'm planning to host my application in a shared web hosting, which has these limitations (most likely similar to PHP + Comet (long-polling) scaling / hosts ): It does not seem I can change the web server. Most likely it's using Apache. Supports MySQL 5, PHP 5.3.x, Perl, Python, Ruby on Rails, CGI (To be more precise, I'll be using HawkHost's shared web hosting.) And here are my result of research, followed by my questions: Some

I have a question about how to load balance web sockets. I have a server which supports web sockets. Browsers connect to my site and each one opens a web socket to www.mydomain.com . That way, my social network app can push messages to the clients. Traditionally, using just HTTP requests, I would scale up by adding a second server and a load balancer in front of the two web servers. With web sockets, the connection has to be directly with the web server, not the load balancers, because if a machine has a physical limit of say 64k open ports, and the clients were connecting to the load balancer

What's the best way to push info from a server to a web client? I know it's possible to setup sockets with Silverlight and Flash but I want to stay way from those two technologies. Gmail seems to do a great job of polling the servers for updated emails and even their chat programs work great (all working in my web browser). Any ideas on the best way to do something like this but using asp.net? Edit: If I have to poll, i'd like to poll the server every 2 or 3 seconds. So I'm not sure how to do this without bringing the web server to it's knees under heavy usage. Christoph Since you mention ASP

I'm trying to implement server push in my Flask project following this tutorial . I've set it all up with no errors, however when I go to the /stream page, Firefox recognizes it as a file and tries to download it. In Safari it just prints out the data sent. I tried adapting the code to a simpler implementation, where a thread just yields some data each second, however it produced the same results. My goal is for each time a python script reaches a point in a loop, it will update a progress bar on the web interface. Any help with this would be great. Thanks. Edit: app.py from flask import Flask