On Jul 25, 2011, at 9:55 AM, Bill Burke wrote:
>
>
> On 7/25/11 9:53 AM, Santiago Pericas-Geertsen wrote:
>>
>> On Jul 25, 2011, at 8:31 AM, Bill Burke wrote:
>>
>>> In Resteasy, we do something much simpler than Atmosphere and the app-developer decide how they want to handle responses. Atmosphere seems a little ambitious to add to the spec as it looks like a full messaging solution, but I'm willing to support the addition as it looks kinda cool.
>>
>> We need to decide if want to support "collaborative" applications (like chat) in which messages can be broadcasted to multiple (suspended) connections. On the one hand, these apps are getting ever more popular (with new HTML5 protocols like Server Sent Events and Websockets) and it would be nice to support them; on the other, sending multiple, short messages over the same connection (HTTP streaming) raises some questions in relation to filters, MBR/MBW and the JAX-RS pipeline.
>>
>
> Comet style messages ain't really REST
Not sure I want to get involved in this discussion :) To me the question is whether there's room in the EE platform for another spec that does just that. The servlet API is quite low level and difficult to use --although they are working on some improvements now. Seems natural for developers to look at JAX-RS for solutions. E.g., Atmosphere has a JAX-RS module.
> and we would have to implement an on-the-wire protocol, no?
Apps may use some protocols, I don't think we need to define that.
-- Santiago