[jsr339-experts] Re: JAX-RS 2.0 API for asynchronous server-side request processing

Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ] [ by messages with attachments ]

From: Markus KARG <markus_at_headcrashing.eu>
Date: Thu, 4 Aug 2011 20:12:11 +0200

+1

> -----Original Message-----
> From: Bill Burke [mailto:bburke_at_redhat.com]
> Sent: Mittwoch, 3. August 2011 20:53
> To: jsr339-experts_at_jax-rs-spec.java.net
> Subject: [jsr339-experts] Re: JAX-RS 2.0 API for asynchronous server-
> side request processing
>
>
>
> On 8/3/11 12:34 PM, Markus KARG wrote:
> >
> > So you actually want that JAX-RS users provide their own executor
> service? I just cannot imagine a JAX-RS user who would have the time to
> provide a better executor service than the Java SE and Java EE teams.
> You seem to expect multithreading professionals among your users.
> >
>
> JAX-RS implementation may not be using an executor service. For
> example, a chat service. The thread that handles the POST to a chat
> might handle propogating the chat message to clients blocking on a GET.
>
> Again, I'll reiterate that I don't think we should get into the pub/sub
> business. Write a simple callback abstraction like Resteasy's and be
> done with it. Pub/Sub is better left to projects like Errai, specs
> like
> JMS and CDI, and protocols like Comet and WebSockets.
>
> --
> Bill Burke
> JBoss, a division of Red Hat
> http://bill.burkecentral.com