This actually sounds quite interesting. We have been talking a bit here about using AngularJS or EmberJS in some projects (still with Tapestry/Cayenne in the background) and if there were better ways to have JS get data from the server, that would be pretty sweet.
One of my biggest concerns with AngularJS/etc is the fact I'd have to duplicate effort. Manage an object graph on the server, on the client, and marshall the data between the two. A big win for us currently with Tapestry is we have one t:value="a.b.c" and Tapestry reads/writes through Cayenne with only one path specified and no duplication to keep values synced up. mrg On Sun, Aug 31, 2014 at 11:26 AM, Andrus Adamchik <and...@objectstyle.org> wrote: > After a marathon of 5 LinkRest [1,2] releases in the last 20 days, I am > starting to think it soon might become capable enough to replace Hessian in > ROP. Which is going to be awesome, as the same server will be able to work > with either Swing/SWT or JS clients, and ROP may break out of its current > shrinking niche. > > Aside from the protocol details, the biggest architectural difference > between current ROP and LinkRest is that the later is not based on blind > serialization. Instead it has a well-defined query API that the client > would have to follow. SelectQuery, RelationshipQuery, ObjectIdQuery will > all be easily translatable to LinkRest. As well as commits (after PATCH [3] > is implemented). Some consequences of the above: > > * A LinkRest server can have fine-grained security. To a point of shaping > the response objects and attributes per user role. We’ve done that already > on a number of real projects. > * A LinkRest server can be upgraded without upgrading all the clients. > E.g. we can use newer Cayenne version on the server and the client wouldn’t > know. > > I am working on improving LinkRest now, and don’t have immediate plans to > jump on the ROP adapter for that, but still wanted to gauge interest in > such a technology. And of course in a wider LinkRest discussion. > > Andrus > > > [1] https://github.com/nhl/link-rest > [2] https://twitter.com/andrus_a > [3] https://github.com/nhl/link-rest/issues/39 > > >
