On 28.08.2013, at 23:46, Bill Burke wrote:
> JAX-RS is a stream, BIO, framework , so it is still using java.io.*.
> Can't get around this.
Doh - sure. Well, 3.0 then :-)
> Its a buffer exchange between Netty and
> Resteasy. Kristoffer just implemented Netty 4 support. He also
> impleme
JAX-RS is a stream, BIO, framework , so it is still using java.io.*.
Can't get around this. Its a buffer exchange between Netty and
Resteasy. Kristoffer just implemented Netty 4 support. He also
implemented support for JAX-RS 2.0 async APIs too. The problem is
though, even with those async
Hi all, Bill,
I saw you integrated RESTEasy and netty[1].
Can you point me to details how directly RESTEasy sits on top of netty?
Is the integration just to enable use of netty as the container or si RESTEasy
actually taking advantage of the async approach?
I am only about to dive into netty
