Bill Burke wrote:
>
>
> Paul Sandoz wrote:
>>
>>>
>>> For a client API I was thinking more of:
>>>
>>> http://wiki.jboss.org/wiki/Wiki.jsp?page=RESTeasyClientFramework
>>>
>>> Where you could re-use jax-rs annotations and providers on an
>>> interface to create a proxy. What we have implemented still needs
>>> some work, but you probably get the gist.
>>>
>>
>> The key difference i see is this: the Jersey client API focuses on the
>> uniform interface constraint; and the RESTeasy client framework
>> focuses on service-specific Java artifacts.
>>
>
> The client API that I've done breaks the uniform interface constraint at
> all or focuses on connecting to a Java server. Or maybe I'm
> misunderstanding you? Its just the mirror opposite from server api.
> Instead of mapping an incoming HTTP request to a method invocation, it
> maps a method invocation to an HTTP request. It can pretty much invoke
> on any HTTP endpoint.
>
LOL, sorry, I should have said the "the client API that I've done
*doesn't* break the uniform interface".
Bill
--
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com