Yep, the video and that sample app should give you a good feel of what this is.
Regarding the site... I've been working on turning LR into a proper open source project lately. Almost there :) So if you've been to the site some time ago, you may check it out again. It has much more useful stuff now. Namely "Documentation" and "Forum" links: * Documentation was added just recently (like this weekend). Still need to document more advanced scenarios, but the basic API's are explained already. * Also recently started a mailing list - https://groups.google.com/forum/?#!forum/linkrest-user, so if you have questions how to implement this or that scenario, let's start a discussion there. Andrus > On Sep 16, 2015, at 5:12 PM, Michael Gentry <[email protected]> wrote: > > I was looking at the LinkRest site, but it wasn't too helpful to me. I'll > look at the WOWODC and sample app links. > > Thanks, > > mrg > > > On Wed, Sep 16, 2015 at 5:07 PM, Andrus Adamchik <[email protected]> > wrote: > >> The short answer is LinkRest. It deals very well with large object graphs >> (pagination, filtering of relationships, etc.). It is also fully integrated >> with Cayenne, so you just take your existing DataMap and start writing the >> endpoints. >> >> Some links: >> >> LinkRest Site: http://nhl.github.io/link-rest/ >> A WOWODC talk: https://www.youtube.com/watch?v=Zwf9Xy90-8s >> A sample app: https://github.com/andrus/link-rest-cms-demo >> >> Andrus >> >> >>> On Sep 16, 2015, at 4:53 PM, Michael Gentry <[email protected]> >> wrote: >>> >>> Branching off from "Syncing peers in single thread", where Andrus said: >>> >>> "I like using REST and keeping state on the client (e.g. the browser) :) >>> But Tapestry 5.x is actually has very decent page state management >>> facilities." >>> >>> We are looking to become more RESTful in some of our Tapestry 5 >>> applications and I'm wondering if anyone has any good suggestions for how >>> to marry REST + Cayenne together, especially when you are dealing with >>> large object graphs? >>> >>> Thanks, >>> >>> mrg >>> >>> PS. Large object graphs = potentially 100s to 1000s of objects in, >>> potentially, more than 100 tables/entities. >> >>
