http://pezra.barelyenough.org/blog/2006/03/another-rest-controller-for-rails/ Sun, 27 Jul 2008 00:53:42 +0000 http://wordpress.org/?v=2.5 http://pezra.barelyenough.org/blog/2006/03/another-rest-controller-for-rails/#comment-11267 stone mind » toward a RESTful approach to Django applications Thu, 01 Mar 2007 11:45:37 +0000 http://pezra.barelyenough.org/blog/?p=218#comment-11267 <p>[...] Or, consider this discussion from Peter Williams’ blog about how to handle a POST that fails validation in the section “Handling Bad Data”: The fundamental problem here is that the separate editor resource will PUT the modified resource when you click save/submit. But what if you messed it up and, say, violated the business rule that blue products must have a price that is divisible by three? In a normal Rails app that proposed change would fail validation and the update action would just re-render the edit page with bad fields highlighted. But in a RESTful world the editor and the validation code are separate and it is wrong from REST stand point to just render the editor resource from in response to a product resource request. However, if you don’t do that you need to get the form data, and which fields are bad, from the previous attempt so that you can re-render the editor with the information the user previously entered and what was wrong with it. [...]</p> […] Or, consider this discussion from Peter Williams’ blog about how to handle a POST that fails validation in the section “Handling Bad Data”: The fundamental problem here is that the separate editor resource will PUT the modified resource when you click save/submit. But what if you messed it up and, say, violated the business rule that blue products must have a price that is divisible by three? In a normal Rails app that proposed change would fail validation and the update action would just re-render the edit page with bad fields highlighted. But in a RESTful world the editor and the validation code are separate and it is wrong from REST stand point to just render the editor resource from in response to a product resource request. However, if you don’t do that you need to get the form data, and which fields are bad, from the previous attempt so that you can re-render the editor with the information the user previously entered and what was wrong with it. […]

]]> http://pezra.barelyenough.org/blog/2006/03/another-rest-controller-for-rails/#comment-4820 RESTful Rails, simply_restful,... Fri, 08 Dec 2006 01:26:36 +0000 http://pezra.barelyenough.org/blog/?p=218#comment-4820 <p>[...] REST is all about resources, remember? SOAP and all other kinds of RPC are evil and we came to the conclusion that a well-defined domain model plus four standard methods of communicating with its instances are key, right? Why the heck are the endpoints to our RESTful URIs still Controllers? Why do we define behavior here – isn’t REST about data? [...]</p> […] REST is all about resources, remember? SOAP and all other kinds of RPC are evil and we came to the conclusion that a well-defined domain model plus four standard methods of communicating with its instances are key, right? Why the heck are the endpoints to our RESTful URIs still Controllers? Why do we define behavior here – isn’t REST about data? […]

]]>