<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Mar 28, 2013, at 8:03 AM, Christos Vasilakis <<a href="mailto:cvasilak@gmail.com">cvasilak@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><meta http-equiv="Content-Type" content="text/html charset=windows-1252"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Hi team,<div><br></div><div>on the last couple of days I have been playing with the idea on how to support nested path in resources (a.k.a subresources). I am more keen in the idea to treat the nested resources as full-time citizens. That is, treat the nested resource as a Pipe.</div></div></blockquote><div><br></div><div><br></div><div>interesting concept </div><br><blockquote type="cite"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><br></div><div>I came up with the following proposal (showing here in iOS)</div><div><br></div><div>For demonstration I use an imaginative Soccer API</div><div><br></div><div>e.g.</div><div><a href="http://soccer.org/leagues/">soccer.org/leagues/</a>{id}/teams/{id}/players</div><div><br></div><div>when expanded with sample {ids}:</div><div><a href="http://soccer.org/leagues/seattle/teams/trebuchet/players">soccer.org/leagues/seattle/teams/trebuchet/players</a></div><div><br></div><div>During registration of the "parent pipe" (leagues) we specify the nested resources for this Pipe using the "setNestedPipes" config option. Internally the Pipeline during the setup of this pipe creates the corresponding nested pipes, initialising their URL accordingly.</div><div><br></div><div>e.g.</div><div>-----</div><div>AGPipeline* pipeline = [AGPipeline pipelineWithBaseURL:BASE_SOCCER_APP_URL];</div><div><div><br></div><div>id<AGPipe> leagues = [pipeline pipe:^(id<AGPipeConfig> config) {</div><div> [config setName:@"leagues"];</div><div><br></div><div> [config setNestedPipes:[@"teams", @"players"]; // an array of nested resources for this pipe</div></div></div></blockquote><div><br></div><div>so since these are essentially pipes, how far can they be configured. for example, could they have callbacks. and yes, i know that makes no sense </div><div><br></div><br><blockquote type="cite"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div>}];</div></div><div>-----</div><div><br></div><div>A new "pipe" method is added in the pipeline with params the Parent ID's of this nested resource. Once returned you have a fill Pipe to invoke operations on.</div><div><br></div><div>-----</div><div><a href="http://soccer.org/leagues/seattle/teams/trebuchet">soccer.org/leagues/seattle/teams/trebuchet</a> - > </div><div><span class="Apple-tab-span" style="white-space: pre; "> </span>[[pipeline pipe:@"teams" pathParams:@[@"seattle"]] <b>read:@</b>"trebuchet"] ...</div><div><br></div><div><a href="http://soccer.org/leagues/seattle/teams/trebuchet/players/foo">soccer.org/leagues/seattle/teams/trebuchet/players/foo</a> - ></div><div><span class="Apple-tab-span" style="white-space:pre"> </span> [[pipeline pipe:@"players" pathParams:@[@"seattle", @"trebuchet"]] <b>read</b>:@"foo"] ..</div><div>-----</div><div><br></div><div><br></div><div>Wdyt?</div><div><br></div><div>Thanks</div><div>Christos</div><div><br></div><div>On Mar 18, 2013, at 1:12 PM, Sebastien Blanc <<a href="mailto:scm.blanc@gmail.com">scm.blanc@gmail.com</a>> wrote:</div><div><div><br class="Apple-interchange-newline"><blockquote type="cite">Well, that would not be possible, for that you will have to create a "child" pipe. But I agree, that is maybe no optimal ...<div><br><br><div class="gmail_quote">On Fri, Mar 15, 2013 at 6:44 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:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000"><div class="im">
<div>On 03/15/2013 01:34 PM, Sebastien Blanc
wrote:<br>
</div>
<blockquote type="cite">I like the idea but I will more see that has a
method/function for the pipelineManager (and will be easier to
implement in JS, I think) :
<div><br>
</div>
<div>var myParentPipe =
Aerogear.Pipeline({name:"parentPipe"}).pipes.parentPipe</div>
<div><br>
</div>
<div>var myChildPipe = Aerogear.Pipeline.fromParent(myParentPipe,
{options} )</div>
</blockquote></div>
What would it look like to get a child record from a parent?<div><div class="h5"><br>
<blockquote type="cite">
<div> <br>
<br>
<div class="gmail_quote">On Fri, Mar 15, 2013 at 5:37 PM,
Douglas Campos <span dir="ltr"><<a href="mailto:qmx@qmx.me" target="_blank">qmx@qmx.me</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">What about
this?<br>
<br>
Pipeline<Post> postPipeline = …<br>
Post post = // get from the pipeline<br>
Pipeline<Comment>
postPipeline.childPipelineForOrOtherWeirdName(Comment.class,
post)<br>
<div>
<div><br>
<br>
On 15/03/2013, at 12:26, Summers Pittman <<a href="mailto:supittma@redhat.com" target="_blank">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" target="_blank">scm.blanc@gmail.com</a>>
wrote:<br>
>> Hi,<br>
>> While I was playing with scaffolding and tried
to build a simple Blog Application with Aerogear I faced
the current situation :<br>
>> I have a Post object which contains many
Comment objects. Now I want to call my Post pipe to
retrieve the related comments, I have currently 2
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 pattern (at least for JS
and iOs, confirmed by Matzew). When doing a read we can
pass an id option but as mentioned in the doc, this id
will always 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 sure how to specify this in
our API, so if you have any ideas feedback 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 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] <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" target="_blank">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" target="_blank">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" target="_blank">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>
</div>
</div>
-- qmx<br>
<div>
<div><br>
<br>
_______________________________________________<br>
aerogear-dev mailing list<br>
<a href="mailto:aerogear-dev@lists.jboss.org" target="_blank">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>
</div>
</div>
</blockquote>
</div>
<br>
</div>
<br>
<fieldset></fieldset>
<br>
<pre>_______________________________________________
aerogear-dev mailing list
<a href="mailto:aerogear-dev@lists.jboss.org" target="_blank">aerogear-dev@lists.jboss.org</a>
<a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a></pre>
</blockquote>
<br>
</div></div></div>
<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></blockquote></div><br></div>
_______________________________________________<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">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a></blockquote></div><br></div></div>_______________________________________________<br>aerogear-dev mailing list<br><a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>https://lists.jboss.org/mailman/listinfo/aerogear-dev</blockquote></div><br></body></html>