<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Apr 4, 2013 at 4:52 PM, Summers Pittman <span dir="ltr"><<a href="mailto:supittma@redhat.com" target="_blank">supittma@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">What if we create a new metaphor, a Junction.<br>
<br>
<a href="https://gist.github.com/secondsun/dcf5682b6ff17c729d9a" target="_blank">https://gist.github.com/secondsun/dcf5682b6ff17c729d9a</a><br>
<br></blockquote><div><br></div><div><br></div><div style>hrm, not sure...</div><div style><br></div><div style>One question:</div><div style><a href="https://gist.github.com/secondsun/dcf5682b6ff17c729d9a#file-junctionapplication-java-L19">https://gist.github.com/secondsun/dcf5682b6ff17c729d9a#file-junctionapplication-java-L19</a><br>
</div><div style>Is that something like a "get('team')" and than read the nested "players" resource/collection?</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
It joins two pipes together and can be used over and over again with different data?<br>
It isn't a Pipe though, but perhaps that could be changed to look more like Christos's previous example.<br>
<br>
At the very least I like the words "junction" or "join" more than "of"<br>
<div class=""><div class="h5"><br>
----- Original Message -----<br>
| From: "Christos Vasilakis" <<a href="mailto:cvasilak@gmail.com">cvasilak@gmail.com</a>><br>
| To: "AeroGear Developer Mailing List" <<a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a>><br>
| Sent: Wednesday, April 3, 2013 3:03:02 AM<br>
| Subject: Re: [aerogear-dev] [Aerogear Pipeline] Support for nested endpoints<br>
|<br>
|<br>
| On Apr 2, 2013, at 4:03 PM, Matthias Wessendorf < <a href="mailto:matzew@apache.org">matzew@apache.org</a> > wrote:<br>
|<br>
|<br>
|<br>
|<br>
| Two thoughts....<br>
|<br>
| 1) the 'original' leaguesPipe has no clue about the subpipes, right ?<br>
| 2) should a pipe offer a 'getter' for all it's sub pipes ?<br>
|<br>
|<br>
| Just a thought is instead of using Pipe, to continue using Pipeline adding an<br>
| extra parameter " of" for specifying the parent : E.g.:<br>
|<br>
| …..<br>
| id<AGPipe> leaguesPipe = [pipeline pipe@"leagues"];<br>
|<br>
| id<AGPipe> allTeamsInSeattlePipe = [pipeline subPipe@"teams" of :leaguesPipe<br>
| for:@"seattle"]<br>
|<br>
| id<AGPipe> allPlayersInTrebuchetPipe = [pipeline subPipe:@"players" of:<br>
| allTeamsInSeattlePipe for:@"trebuchet"];<br>
| …..<br>
|<br>
|<br>
| Wdyt?<br>
|<br>
|<br>
|<br>
|<br>
|<br>
|<br>
|<br>
| -M<br>
|<br>
|<br>
|<br>
|<br>
|<br>
| Thanks,<br>
| Christos<br>
|<br>
|<br>
|<br>
|<br>
|<br>
|<br>
|<br>
|<br>
|<br>
|<br>
|<br>
|<br>
|<br>
|<br>
| <a href="http://soccer.org/leagues/seattle/teams/trebuchet/players/foo" target="_blank">soccer.org/leagues/seattle/teams/trebuchet/players/foo</a> - ><br>
| [[pipeline pipe:@"players" pathParams:@[@"seattle", @"trebuchet"]] read<br>
| :@"foo"] ..<br>
| -----<br>
|<br>
|<br>
| Wdyt?<br>
|<br>
| Thanks<br>
| Christos<br>
|<br>
| On Mar 18, 2013, at 1:12 PM, Sebastien Blanc < <a href="mailto:scm.blanc@gmail.com">scm.blanc@gmail.com</a> > wrote:<br>
|<br>
|<br>
|<br>
| Well, that would not be possible, for that you will have to create a "child"<br>
| pipe. But I agree, that is maybe no optimal ...<br>
|<br>
|<br>
| On Fri, Mar 15, 2013 at 6:44 PM, Summers Pittman < <a href="mailto:supittma@redhat.com">supittma@redhat.com</a> ><br>
| wrote:<br>
|<br>
|<br>
|<br>
| On 03/15/2013 01:34 PM, Sebastien Blanc wrote:<br>
|<br>
|<br>
| I like the idea but I will more see that has a method/function for the<br>
| pipelineManager (and will be easier to implement in JS, I think) :<br>
|<br>
| var myParentPipe = Aerogear.Pipeline({name:"parentPipe"}).pipes.parentPipe<br>
|<br>
| var myChildPipe = Aerogear.Pipeline.fromParent(myParentPipe, {options} )<br>
| What would it look like to get a child record from a parent?<br>
|<br>
|<br>
|<br>
|<br>
|<br>
|<br>
| On Fri, Mar 15, 2013 at 5:37 PM, Douglas Campos < <a href="mailto:qmx@qmx.me">qmx@qmx.me</a> > wrote:<br>
|<br>
|<br>
| What about this?<br>
|<br>
| Pipeline<Post> postPipeline = …<br>
| Post post = // get from the pipeline<br>
| Pipeline<Comment><br>
| postPipeline.childPipelineForOrOtherWeirdName(Comment.class, post)<br>
|<br>
|<br>
| On 15/03/2013, at 12:26, Summers Pittman < <a href="mailto:supittma@redhat.com">supittma@redhat.com</a> > wrote:<br>
|<br>
| > On 03/14/2013 04:48 AM, Matthias Wessendorf wrote:<br>
| >><br>
| >><br>
| >> On Thu, Mar 14, 2013 at 9:32 AM, Sebastien Blanc < <a href="mailto:scm.blanc@gmail.com">scm.blanc@gmail.com</a> ><br>
| >> wrote:<br>
| >> Hi,<br>
| >> While I was playing with scaffolding and tried to build a simple Blog<br>
| >> Application with Aerogear I faced the current situation :<br>
| >> I have a Post object which contains many Comment objects. Now I want to<br>
| >> call my Post pipe to retrieve the related comments, I have currently 2<br>
| >> options :<br>
| >><br>
| >> /posts/1 -> assuming comments will be implicitly retrieved (eager loading)<br>
| >> /comments/?postid=1<br>
| >><br>
| >> But regarding our model the correct form should be :<br>
| >><br>
| >> /posts/1/comments<br>
| >><br>
| >><br>
| >> +1<br>
| >> that is the ideal way to model URIs for "nested" resources.<br>
| >><br>
| >> See [1], extracted from [2]<br>
| >><br>
| >><br>
| >><br>
| >> But, AFAIK, with the current API, it is not possible to define this last<br>
| >> pattern (at least for JS and iOs, confirmed by Matzew). When doing a read<br>
| >> we can pass an id option but as mentioned in the doc, this id will always<br>
| >> be append to the endpoint.<br>
| >><br>
| >><br>
| >> Well, it is possible - but in a very (IMO) ugly way:<br>
| >><br>
| >> <a href="https://gist.github.com/matzew/6ab432e437b9a017a21d" target="_blank">https://gist.github.com/matzew/6ab432e437b9a017a21d</a><br>
| >><br>
| >><br>
| >><br>
| >><br>
| >> IMO, we should be able to support this pattern but for now I'm not really<br>
| >> sure how to specify this in our API, so if you have any ideas feedback<br>
| >> this thread has been made for you !<br>
| >><br>
| >><br>
| >><br>
| >> Suggestion: Enhance the read function - example:<br>
| >><br>
| >> <a href="https://gist.github.com/matzew/04f069dfbed2cc77a8b4" target="_blank">https://gist.github.com/matzew/04f069dfbed2cc77a8b4</a><br>
| > I'm thinking of the inverse myself. Add a "ParentPath" property which can<br>
| > be used to extract information from parent objects.<br>
| ><br>
| > <a href="https://gist.github.com/secondsun/17ce96082eda37dbd10e" target="_blank">https://gist.github.com/secondsun/17ce96082eda37dbd10e</a><br>
| ><br>
| >><br>
| >><br>
| >> -Matthias<br>
| >><br>
| >><br>
| >> [1]<br>
| >> <a href="http://www.infoq.com/resource/articles/rest-introduction/en/resources/figure2.jpg" target="_blank">http://www.infoq.com/resource/articles/rest-introduction/en/resources/figure2.jpg</a><br>
| >> [2] <a href="http://www.infoq.com/articles/rest-introduction" target="_blank">http://www.infoq.com/articles/rest-introduction</a><br>
| >><br>
| >><br>
| >><br>
| >><br>
| >> Seb<br>
| >><br>
| >><br>
| >> _______________________________________________<br>
| >> aerogear-dev mailing list<br>
| >> <a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
| >> <a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br>
| >><br>
| >><br>
| >><br>
| >> --<br>
| >> Matthias Wessendorf<br>
| >><br>
| >> blog: <a href="http://matthiaswessendorf.wordpress.com/" target="_blank">http://matthiaswessendorf.wordpress.com/</a><br>
| >> sessions: <a href="http://www.slideshare.net/mwessendorf" target="_blank">http://www.slideshare.net/mwessendorf</a><br>
| >> twitter: <a href="http://twitter.com/mwessendorf" target="_blank">http://twitter.com/mwessendorf</a><br>
| >><br>
| >> _______________________________________________<br>
| >> aerogear-dev mailing list<br>
| >><br>
| >> <a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
| >> <a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br>
| ><br>
| > _______________________________________________<br>
| > aerogear-dev mailing list<br>
| > <a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
| > <a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br>
|<br>
| -- qmx<br>
|<br>
|<br>
| _______________________________________________<br>
| aerogear-dev mailing list<br>
| <a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
| <a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br>
|<br>
|<br>
|<br>
| _______________________________________________<br>
| aerogear-dev mailing list <a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
| <a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br>
|<br>
|<br>
| _______________________________________________<br>
| aerogear-dev mailing list<br>
| <a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
| <a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br>
|<br>
| _______________________________________________<br>
| aerogear-dev mailing list<br>
| <a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
| <a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br>
|<br>
|<br>
| _______________________________________________<br>
| aerogear-dev mailing list<br>
| <a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
| <a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br>
|<br>
|<br>
|<br>
| --<br>
| Matthias Wessendorf<br>
|<br>
| blog: <a href="http://matthiaswessendorf.wordpress.com/" target="_blank">http://matthiaswessendorf.wordpress.com/</a><br>
| sessions: <a href="http://www.slideshare.net/mwessendorf" target="_blank">http://www.slideshare.net/mwessendorf</a><br>
| twitter: <a href="http://twitter.com/mwessendorf" target="_blank">http://twitter.com/mwessendorf</a><br>
| _______________________________________________<br>
| aerogear-dev mailing list<br>
| <a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
| <a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br>
|<br>
|<br>
| _______________________________________________<br>
| aerogear-dev mailing list<br>
| <a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
| <a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br>
|<br>
|<br>
|<br>
| --<br>
| Matthias Wessendorf<br>
|<br>
| blog: <a href="http://matthiaswessendorf.wordpress.com/" target="_blank">http://matthiaswessendorf.wordpress.com/</a><br>
| sessions: <a href="http://www.slideshare.net/mwessendorf" target="_blank">http://www.slideshare.net/mwessendorf</a><br>
| twitter: <a href="http://twitter.com/mwessendorf" target="_blank">http://twitter.com/mwessendorf</a><br>
| _______________________________________________<br>
| aerogear-dev mailing list<br>
| <a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
| <a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br>
|<br>
|<br>
| _______________________________________________<br>
| aerogear-dev mailing list<br>
| <a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
| <a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br>
<br>
_______________________________________________<br>
aerogear-dev mailing list<br>
<a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a></div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br>Matthias Wessendorf <br>
<br>blog: <a href="http://matthiaswessendorf.wordpress.com/" target="_blank">http://matthiaswessendorf.wordpress.com/</a><br>sessions: <a href="http://www.slideshare.net/mwessendorf" target="_blank">http://www.slideshare.net/mwessendorf</a><br>
twitter: <a href="http://twitter.com/mwessendorf" target="_blank">http://twitter.com/mwessendorf</a>
</div></div>