server-push

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? Daniel Vassallo Does that mean the server push hack called Comet will be obsolete? WebSockets are capable of replacing Comet, AJAX, Long Polling, and all the hacks to workaround the problem when web browsers could not open a simple socket for bi

for SPDY, we need to implement a PushStrategy and to register it to push resources. What about HTTP2 support? I like the idea of nginx which consists to read link header in the HTTP response: https://nghttp2.org/blog/2015/02/10/nghttp2-dot-org-enabled-http2-server-push/ Thanks! Jetty HTTP/2 comes with full support for HTTP/2 Push, in fact in different flavors. Webtide's website already has Jetty's HTTP/2 Push enabled. There is a PushCacheFilter , which implements the same algorithm that was implemented in Jetty SPDY's PushStrategy, based on the Referer header. There is a PushSessionCacheFilter

How can I implement the comet / server push design pattern using PHP and Javascript? Essentially what I would like is something like this: User clicks a 'submit' button Javascript shows a message like 'Processing 0 / 100 items' Whenever a new item is processed, the php / server pushes out an update, and the javascript changes the message to 'Processing 2/100 items, 3/100 items, and so on'. How can I do this? Any links/info please? Comet with PHP has some tricky issues with scaling. An alternative would be a SaaS solution, such as WebSync On-Demand . (Disclaimer: I work there). That way you don

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 events which are more useful to my application, I'm trying one called 'update'. Here's is my basic

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 reconnecting forever, not only once. The browser is Firefox. I deal with this by implementing a keep-alive

Lead by several examples and questions answered here ( mainly http://www.javaworld.com/javaworld/jw-02-2009/jw-02-servlet3.html?page=3 ), I want to have server sending the response multiple times to a client without completing the request. When request times out, I create another one and so on. I want to avoid long polling, since I have to recreate request every time I get the response. (and that quite isn't what async capabilities of servlet 3.0 are aiming at). I have this on server side: @WebServlet(urlPatterns = {"/home"}, name = "async", asyncSupported = true) public class CometServlet

Read about Server push here . I want to push data to client from my web application in real time. I was looking at TCP sockets as one of the options. For HTTP I found a variety of frameworks for Java, PHP, Python and others over here . However I don't know whether any of these support Push. What options and frameworks would you suggest for implementing Server push? What language would you advocate for implementing the same and why? I'm using Orbited right now, it's great! If you are doing chat or subscription type stuff use stompservice and orbited. If you are doing 1 to 1 client mapping use

The HTTP/2 specification indicates that any resource identified in a PUSH_PROMISE frame won't be pushed if the client cancels it. When a browser detects a resource already in the cache, it should cancel the push for this resource. However, I don't see how the browser can detect it. Do the frames provide additional informations like etag or last modified to allow the browser to detect if any cache entry must be evicted or if the push could be canceled? If it's possible, some bandwidth could be saved. However, it seems server-push compromises any client cache optimization. In HTTP/2 the server