On 5/23/11 10:26 AM, Santiago Pericas-Geertsen wrote:
>
> On May 23, 2011, at 6:16 AM, algermissen1971 wrote:
>
>>>
>>> Regarding JAX-RS 2.0 what would be neccessary is an HTTP client connector class abstraction that is defined outside of JAX-RS (for example being part of Java SE).
>>>
>>> JAX-RS could build on top of that and steer clear of all issues around connection management and caching.
>>>
>>> Question is, what the ideal place for both would be
>>
>> For example, how big would be the hurdle to add HTTP client connectors as a first class citizen to Java SE in a new package
>>
>> javax.http
>
> It's hard for me to answer this question. I believe a better HTTP stack has been an SE RFE for some time. You could post this question to the JSR 337 (SE 8) EG --still under formation according to the JSR's page.
>
+1. I'd like to see what we're doing in the JAX-RS client API be moved
and married to the JDK. Thats why I think it is important to be able to
cleanly separate the clietn and server apis of JAX-RS.
--
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com