On Mar 6, 2014, at 2:07 PM, Bill Burke <bburke_at_redhat.com> wrote:
>
>
> On 3/6/2014 11:25 AM, Santiago Pericas-Geertsen wrote:
>>
>> On Mar 6, 2014, at 10:56 AM, Bill Burke <bburke_at_redhat.com> wrote:
>>
>>>
>>>>> What would be awkward is having support for a non-HTTP session-based
>>>>> protocol inside of a REST framework.
>>>>
>>>> I would agree. Except SSE _is designed_ to work on HTTP and it is how
>>>> HTML5 clients use it. I think you're mixing up SSE with WebSockets.
>>>> Please take a look at the specification:
>>>>
>>>> http://www.w3.org/TR/eventsource/
>>>>
>>>
>>> I did look at the spec. It is session based. Its standardized Comet.
>>
>> Yes, but I don't get your point about sessions. Is streaming a resource using the standard JAX-RS API session based?
>>
>
> REST is stateless == no sessions
And there are no sessions in SSE, only longer-lived streaming connections. JAX-RS resource instances don't need anything beyond the default request scope to support this.
-- Santiago