On Tue, Jan 15, 2013 at 12:17 PM, Sebastien Blanc <scm.blanc@gmail.com> wrote:

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)

a huge +1 !

I *think* that this "limitation" was introduced when porting the iOS API 1-by1

(In iOS I can't do a similar overload (since we already have a [read:success:failure], which queries for a specific ID))

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@apache.org> wrote:
https://gist.github.com/4532661

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