We used GAE cursors for the Expenses sample that ships with GWT. Take a look at the code in Report#findReportEntriesBySearch: http://code.google.com/p/google-web-toolkit/source/browse/trunk/samples/expenses/src/main/java/com/google/gwt/sample/expenses/server/domain/Report.java
I don't know exactly how the code works, but it looks like we cache cursors on the server so we can reuse them later to fulfill a repeated query. <http://code.google.com/p/google-web-toolkit/source/browse/trunk/samples/expenses/src/main/java/com/google/gwt/sample/expenses/server/domain/Report.java> Thanks, John LaBanca jlaba...@google.com On Wed, Feb 2, 2011 at 4:14 AM, George Moschovitis < george.moschovi...@gmail.com> wrote: > I know how GAE datastore paging works... > > I am looking to make this work in the context of GWT. I thought about a > scheme of keeping old cursors, but I am wondering if there is a > better/cleaner solution. > > -g. > > -- > You received this message because you are subscribed to the Google Groups > "Google Web Toolkit" group. > To post to this group, send email to google-web-toolkit@googlegroups.com. > To unsubscribe from this group, send email to > google-web-toolkit+unsubscr...@googlegroups.com<google-web-toolkit%2bunsubscr...@googlegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/google-web-toolkit?hl=en. > -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
