|Re: [jetty-users] Jetty client|
Not sure about your question here.
On Thu, Sep 5, 2013 at 6:47 PM, Mikhail Mazursky <ash2kk@xxxxxxxxx> wrote:
> Few questions about Jetty Client:
> 1. Do it support SNI ? For example Apache Http Client do not  and we
> want to switch maybe to Jetty Client or some other.
The client side of SNI is taken care of in modern JDKs, which send the
SNI TLS extension by default to servers.
The current problem in Java is that it is not readable by servers.
> 2. Are there any plans to support JSR-339 ? I think it can be usefull toJSR 339 is about a REST API on the server side.
> abstract implementation and be able to switch them. I found two
> implementations of this JSR - Jersey  (reference implementation) and
> Apache CXF . I'm not sure what the CXF project is but looks like it
> supports this JSR.
I am not sure what you mean here about the client side.
> 3. Do Jetty Client use NIO to do I/O or traditional blocking I/O API? E.g.Jetty's HttpClient is completely based on NIO, completely asynchronous.
> Jersey uses thread pool and traditional I/O to do async requests (AFAIK) and
> this may not suit my needs.
Back to the top