Hi Eric, > I propose that Rails and ActiveResource add support for retrieving a > model's schema via REST. This could make it much easier for REST > clients to auto-figure out attributes, the way that ActiveRecord uses > the database to do the same thing.
+1, I think this is a great idea. Since we're talking about this, I had the idea of using the OPTIONS method to return the methods allowed on a resource (via the Allow header), but also returning an XML representation of the routes for the nested and associated resources. The OPTIONS response is supposed to return a comma separated list of methods allowed in the Allow header, but the body can really be anything we want since the spec doesn't say what it should be. If people think this is a good fit, we could use it as a way of "introspecting" a resource. Combine these two ideas, and we have a way for a remote client to create new resources AND a way of finding all the associated resources. -- Thanks, Dan __________________________________________________________________ Dan Kubb Autopilot Marketing Inc. Email: [EMAIL PROTECTED] Phone: 1 (604) 820-0212 Web: http://autopilotmarketing.com/ __________________________________________________________________ --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---
