Hi Gustav,
Http 1.0 and 1.1 will be in client.
I think you are talking about HTML 5 and web sockets, correct me if I'm
wrong.
I agree that it would be nice to support this kind of bleeding edge
features.
Could you say a bit more about what is needed apart from standard 1.0 and
1.1 features?
Thank you,
Hubert.
On Thu, Apr 23, 2009 at 12:47 PM, gustav trede <
gustav.trede_wsdevel_at_telia.com> wrote:
> 2009/4/23 Oleksiy Stashok <Oleksiy.Stashok_at_sun.com>
>
>> Hi,
>>
>>
>> Hello,
>>
>> I'm having problems coming up with something better for HTTP Client than
>> Jersey Client API.
>>
>> What do you think of using Jersey Http Client API?
>>
>>
>> +1
>>
>> During one of the meetings, when we discussed the Http client API to go
>> with, we came to opinion, that it will make sense to leverage existing HTTP
>> server entities like Request/Response/Cookies etc...
>> Actually I'm fine with Jersey HTTP client API, just wanted to make sure.
>>
>> Thanks.
>>
>> WBR,
>> Alexey.
>>
>>
>>
>> Why not starting with Jersey by removing the use of HttpURL classes from
>> JDK? One way we could do is to copy the 1.0.3 version of Jersey here and
>> make changes here...then later either propose them to use us or maintains
>> the code :-)
>>
>> A+
>>
>> -- Jeanfrancois
>>
>> Cheers,
>>
>> Hubert
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe_at_grizzly.dev.java.net
>> For additional commands, e-mail: dev-help_at_grizzly.dev.java.net
>>
>>
>>
>
>
> http 5 spec in the client would be nice, we need it to do unit tests.
>
> --
> regards
> gustav trede
>
>
>