Charlee.
On 12.09.2013, at 09:45, Charlee Chitsuk <charlee.ch_at_gmail.com> wrote:
> Hi,
>
> I'm not sure if you may have a chance to visit the Chapter 5. Client API[1] or not, it provides us the wrapped usage for communicating to the Jersey Server without the Apache HTTP client. It also provides the Securing a Client[2] for managing the SSL, keystore, truststore and HTTP Basic Authentication Support[3] out of the box as well.
thanks. I have been looking at headlines when I checked the last time. I'll check it out and try to write a blog post about it - it's really kind of hidden in the prose there :-)
BTW, the use of 'transport' here is a bit strange since transport is the 'T' in TCP, not HTTP and I doubt that the idea is that the client implementations provide the TCP layer.
Jan
>
> I hope this may help.
>
> [1] https://jersey.java.net/documentation/latest/client.html
> [2] https://jersey.java.net/documentation/latest/client.html#d0e3189
> [3] https://jersey.java.net/documentation/latest/client.html#d0e3300
>
> --
> Best Regards,
>
> Charlee Ch
>
>
> 2013/9/12 algermissen1971 <algermissen1971_at_mac.com>
> Hi,
>
> I saw (not so easy to find out, actually) that there is ApacheHttpClient support in 2.0.
>
> Can you confirm it has production quality (asking, because it was so quietly released :-) and are there examples of how to use it exactly? I seem unable to find the Jersey client factory or something similar.
>
> Jan
>
>
>