Hi Dan, On Oct 2, 2007, at 10:33 PM, Dan Kubb wrote: > Don't forget the 422 Unprocessable Entity status code. You'd use > it when the request is syntactically valid, but still contains > invalid information. An example of this would be if someone sent > an valid XML document, but one of the elements contained data that > didn't meet the validates_* constraints in a model.
Where is that documented? I didn't see it on: http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html > How about mentioning conventions for searching using query strings > that I've seen in ActiveResource? Any extra params you send through > to the find() method are added to the query string. Here's an article > exploring different conventions for search: http://woss.name/2007/07/22/convention-for-restful-search-in-rails/ That's a great suggestion, but right know there doesn't seem to be any "standard" for how to do it. Many if resource_search gets standardized (and integrated into Rails) then we can make *that* the convention... -- Ernie P. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
