server-push

问题 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

问题 I am struggling for long with push messaging in BlackBerry. I am able to register successfully for push messaging with a returned code of rc=200 . However, when I run the server side code, be it in PHP or .Net, I get a successful returned code but the device never receives the message. My PHP code is as follows: <?php ini_set('display_errors','1'); error_reporting(E_ALL); // APP ID provided by RIM $appid = '3385-xxxxxxxxxxx'; // Password provided by RIM $password = 'xxxxxx'; //Deliver before

问题 I am developing an Android video streaming application using the OkHttp library and HTTP/2. I am investigating the possibility of using the server push functionality of the HTTP/2 protocol, but I am not sure whether OkHttp supports it or not. I have a basic server implementation to test HTTP/2 push, which works without problems on the chrome browser (i.e., pushed content is stored in the cache and retrieved from the cache by the browser). When I use the Android application with the OkHttp

问题 I wonder why it's so difficult to set up a server for live notifications with Comet. Will this ever be implemented in existing frameworks like Rails? It's popularity is huge, but it's still not easy to get it up and running. What options are there for Rails applications today? Thanks 回答1: What about http://pusherapp.com ? 回答2: A single script can be used to get live updates using WebSync On-Demand 来源： https://stackoverflow.com/questions/3375318/when-will-a-framework-be-available-for-comet

问题 Well, I have doubts about this technology, more precisely in its implementation, can not find good examples on the Internet, as it involves javascript and php, only, you would have some links where I can find this stuff really works and that ? 回答1: A great source for all things Comet is Comet Daily. Unfortunately it's not updated all that often any more but there are some fantastic old articles in there. It's contributed to by guys that have been developing Comet solutions for over 10 years.

问题 I am willing to implement a chat website on App Engine. But I found that App Engine will not allow me to go with server push. (as it will kill the response after 30 sec). So whats the other method that can be used? Will polling cause bad user experience? Meaning will the user have to wait for some time to retrieve new messages from the server? What will be the ideal polling interval? If you use very small polling intervals, will my bandwidth get exhausted? Will I suffer performance problems?

问题 It looks like Websockets in HTML 5 will become a new standard for server push. Does that mean the server push hack called Comet will be obsolete? Is there a reason why I should learn how to implement comet when Websockets soon (1-2 years) will be available in all major browsers? Then I could just use Beaconpush or Pusher instead till then right? 回答1: Does that mean the server push hack called Comet will be obsolete? WebSockets are capable of replacing Comet, AJAX, Long Polling, and all the

问题 I've recently discovered EventSource, YUI3 has a Gallery module to normalise and fallback behaviour, that's what I've chosen to go with in my example as I use that framework already. So I've searched about quite a bit, read many blogs, posts and examples, all of which show pretty much the same thing: How to set up basic SSE events. I now have 6 examples of open/message/error/close events firing. What I don't have (what I'd hoped this link was going to give me) is an example of how to fire SSE

问题 is it any simpler way then cometd as long-polling framework for java? Because what I need - is client specifies some parameters and sends them to server. Server process them and starts contonuously pushing messages back to client (looks like Thread-per-Service?). Client receivs messages and displays them. Client has possibility to stop listening and actually stop server's service to send messages. Maybe I'm too lazy, but cometd's examle was not that short and transparent as I wanted it to be.

问题 I am using JavaScript EventSource in my project front-end. Sometimes, the connection between the browser and the server fails or the server crashes. In these cases, EventSource tries to reconnect after 3 seconds, as described in the documentation. But it tries only once. If there is still no connection, the EventSource stops to try reconnection and the user have to refresh the browser window in order to be connected again. How I can prevent this behavior? I need the EventSource to try