| there are two implementations of rest .. the original which did automatic routing combined with entity delegates to control access and to provide optimization points for fetching. this one is the one that is hooked into d2w via anjo's d2rest framework, which, i believe, lets you define rules for what gets returned to the user based on one of its routes.
the other one is the one i showed at wowodc with the custom route system and controllers based on rails. if you use this one, i have no idea how you would interact with it with d2w. it doesn't really make much sense to use d2w with it, really. you could maybe return components that use d2w to render the output? it's kind of an impedance mismatch, though.
On Nov 2, 2009, at 10:26 AM, Daniel Beatty wrote: Greetings Mike, I see. Now if I add routes and a route handler to an existing D2W app, would it also gain use of the "RESTful" functionality, and what part if any of the D2W rule set would effect it?
Thanks. Dan On Nov 2, 2009, at 7:19 AM, Mike Schrag wrote: there is a d2rest framework that Anjo made on top of the old rest implementation ... i don't really know how the new stuff fits with d2w -- probably not very well at the moment, since it's explicitly NOT fully automated. the old one was designed to be much more automatic in exchange for a much more complicated api when you want to customize things. On Nov 2, 2009, at 10:13 AM, Daniel Beatty wrote: Greetings Anjo, Mike, Dave, and other wizards of WO, Say that I am building a D2W app and I want to add RESTful functionality to it. I know from Mike's talk at WOWODC West that I can do it by adding routes for each entity in my model. How do I get it to cooperate with D2W's rule model?
In my case, I am using D2W's rule model to fine grain access to a really poorly designed model that has an overwhelming data set to it. It would be nice that as I fine tune access via D2W, that RESTful side reaps those benefits too.
Any ideas?
Thank you,
|