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