Re: [aerogear-dev] Client Paging Strawman
On 14/01/2013, at 17:48, Summers Pittman <supittma(a)redhat.com> wrote:
> This just feels like we're killing the dynamic nature of JS.
:)
Well this is a an description of a Java implementation.
I lol'd
Instead of a separate PageContext what if readWithFilter() returns a
PagedList which has next() and prev() as methods on it? In java this can implement a list
and be cast at runtime. The only question is does next() return a new PagedList or return
void and update the current pagedlist?
Well, matzew gave me earlier the idea that a PagedResult makes more sense, and calling
next() returns a List<T> with the actual items - avoids casting & stuff but
increases API surface area.
Gotta love tradeoffs
-- qmx