[jax-rs-spec users] [jsr339-experts] Re: Re: How are suspended responses usually managed?

From: Bill Burke <>
Date: Mon, 15 Oct 2012 09:37:05 -0400

On 10/14/2012 9:39 PM, Marek Potociar wrote:
> On Oct 12, 2012, at 9:36 PM, Jan Algermissen <
> <>> wrote:
>> On Oct 12, 2012, at 9:28 PM, Markus KARG wrote:
>>> Jan,
>>> just scanned the public draft of the spec and did not find the word
>>> "push" a
>>> single time! How did you come to the conclusion that the async API will
>>> allow you to implement frequent server pushes ontop of it?
>> I thought that was one of the motivations behind it and Bill mentions
>> it as one in his Oct 9th talk on Infoq.
> FWIW, the original proposal was much more focused on being able to
> broadcast multiple events possibly over the same connection. See here:
> Alas, this was found too complex by some of the experts here and since I
> was alone in supporting the proposal at that time, I have decided to
> come up with a much simpler model. At least for this release.

The problem is, once you go down this path of multiple events per
connection, it ceases to become HTTP and we have to start requiring
support for Websockets and the definition of a message protocol over
websockets. Just seemed way out of scope since we're dealing with REST
web services on top of HTTP.

Bill Burke
JBoss, a division of Red Hat