Re: [aerogear-dev] [Doc] AerogearAndroidPipes101

On Mon, Jun 3, 2013 at 9:48 AM, Sebastien Blanc <scm.blanc(a)gmail.com&gt;wrote: > > > > On Sat, Jun 1, 2013 at 3:56 PM, Apostolos Emmanouilidis < > aemmanou(a)redhat.com&gt; wrote: > >> ** >> >> On Sat, 2013-06-01 at 11:45 +0200, Matthias Wessendorf wrote: >> >> Hi, >> >> >> >> reading [1], I have two questions: >> >> >> >> * the "http://www.server.com/car" URL, shouldn't it be " >> http://www.server.com/cars" (plural)? >> >> ==> and the later mentioned HTTP methods, e.g. "GET:/car" ==> >> "GET:/cars"? >> >> >> I agree that it should be plural >> >> >> >> >> * Do we really promote the direct access to the RestAdapter, instead >> of via the Pipeline ? >> >> ==> Pipe<Car> pipe = new RestAdapter<pipe>(Car.class, new URL(" >> http://www.server.com/")); >> >> >> >> Except that, maybe this line should change to Pipe<Car> pipe = new >> RestAdapter<*Car*>(Car.class, new URL("*http://www.server.com/car*")); >> in order to match the URLs of the described web service. >> > > > I don't know the android details implementation but if we define the URL > like and we call a read after that like pipe.read() won't we end up with > an url like that *http://www.server.com/car/car ? * > yeah, that statement was wrong. I was more concerned, promoting "impl details (RestAdapter) instead of using "public" API: pipeline.pipe(.....); -Matthias > >> >> Thanks! >> >> Matthias >> >> >> >> >> >> [1] aerogear.org/docs/guides/aerogear-android/AerogearAndroidPipes101/ >> >> >> >> _______________________________________________ >> aerogear-dev mailing listaerogear-dev@lists.jboss.orghttps://lists.jboss.org/mailman/listinfo/aerogear-dev >> >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf