[aerogear-dev] Server Contracts and Thoughts about Server-Agnostic Clients
glen at thoughtcraft.com
Sat Sep 15 08:14:39 EDT 2012
On 9/15/12 5:53 AM, Matthias Wessendorf wrote:
> On Fri, Sep 14, 2012 at 10:12 PM, Matthias Wessendorf <matzew at apache.org> wrote:
>> On Friday, September 14, 2012, Glen Daniels wrote:
>>> On 9/13/12 11:25 PM, Douglas Campos wrote:
>>>> - logic name (/vehicles should be interpreted as "cars")
>>> No need to do anything explicit about this, if I'm understanding you
>>> correctly. Taking a Java/Android example, if you want to play with
>>> cars, you could just do:
>>> pipe = new Pipe("vehicles", Car.class);
>> vehicles is a logical name on the client, for the /cars resource (due to the
>> Car type), right?
> Actually, looking at  I see that the "vehicles" is the URI - not a
> logical name on the client :)
> So... something like 'new Pipe("cars", Car.class);' works if the
> server allows an 'alias' (e.g. /cars) for the /vehicles endpoint
> (or the other way around).
> Not sure how having server side aliases is a problem. I guess it's up
> to the 'service provider' as long as the client API can read the
> (working) endpoint URI to work against.
> That said, not sure why one would actually introduce a lot of aliases
> for a single endpoint...
Agreed - it's not a problem at all, but neither do I think we need to
actually do anything about it for AeroGear.
>  https://github.com/gdaniels/android-data/blob/master/android/src/org/aerogear/android/Pipe.java#L41
More information about the aerogear-dev