Hi,
Some aditional remarks on Summers gist :
Instead of :
Pipe.readWithFilter(ReadFilter)
Couldn't we just overload the read() method ? i.e :
read(ReadFilter filter)
About the where property in ReadFilter class :
Do we really want to mix paging and querying ?
About Pipe.getPageContext(List result):
Same remarks as Matthias, not sure to understand how it works (even if I
think I've understand ...)
General remarks about Paging:
Even if it's not in scope for 1.0, I think we have to keep in mind that we
will also be able to do pagination "offline" / "only client side"
(maybe we
would do some paging on a Store element ?) , so we have to consider this
when designing our API.
Seb
On Tue, Jan 15, 2013 at 11:37 AM, Matthias Wessendorf <matzew(a)apache.org>wrote: