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 ...
Seb


On Tue, Jan 15, 2013 at 8:59 PM, Douglas Campos <qmx@qmx.me> wrote:

On 15/01/2013, at 17:40, Summers Pittman <supittma@redhat.com> wrote:

>> 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.
> 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).

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

-- qmx
_______________________________________________
aerogear-dev mailing list
aerogear-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev