From: Stefan Tilkov <stefan.tilkov_at_innoq.com>
Date: Sat, 8 Mar 2008 00:00:15 +0100

On Mar 7, 2008, at 5:49 AM, Bill Burke wrote:

>
>
> 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".
>

Logically, I believe you are right. Still: I have no idea why, but I
share Paul's feeling that it somehow feels "wrong" on the client side
to treat the uniform interface as an implementation detail that's
abstracted away.

Stefan



> Bill
>
> --
> Bill Burke
> JBoss, a division of Red Hat
> http://bill.burkecentral.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_jsr311.dev.java.net
> For additional commands, e-mail: dev-help_at_jsr311.dev.java.net
>
>