I'm sure that we can find an arrangement. I understand Kris's concerns on some points but not always sure that we are all on the same page. I will try to write a snippet in JS that tries to conciliates both worlds. Will may be be tomorrow ...<div>
Seb</div><div><br><br><div class="gmail_quote">On Tue, Jan 15, 2013 at 8:59 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">
<div class="im"><br>
On 15/01/2013, at 17:40, Summers Pittman <<a href="mailto:supittma@redhat.com">supittma@redhat.com</a>> wrote:<br>
<br>
>> Basically, anything that involves creating a new object to maintain paged pipes rather than just using any other pipe and overloading the read method to do paging doesn't make sense to me.<br>
> I'm confused. Your strawman creates extra pipes to maintain paged states. The other proposals all use an overridden read method and return a list which can be used to fetch different pages of data (which is what it sounds like you want).<br>
<br>
</div>This is where things get tricky for our java-rotted minds - everything is mutable in JS, and Kris is (ab)using this on his API freely :P<br>
<br>
-- qmx<br>
<div class="HOEnZb"><div class="h5">_______________________________________________<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>
</div></div></blockquote></div><br></div>