So after I used middleware to make browsers work with RESTful URLs in GAE I started to write more than simple little methods and I’m trying to write a test application. Upon doing so, I ran into a defect with how request parameters are returned for a PUT request To be fair, this is more of a problem with webob than with GAE, but I hope that this gets fixed because my attempts at monkey patching the problem have not worked out too well.
So there was much talk and whathave you about Google’s new App Engine and after viewing the tutorials and reading the documentation, I thought it was pretty rad too. Because I was using rack for some previous stuff, WSGI felt right at home (probably because rack was modeled after WSGI). There was one thing that bothered me however. When writing a class using their webapp framework there isn’t any magic param name, like _method, that I could use to mock requests methods like DELETE and PUT since the browser doesn’t support those HTTP methods.
Well my friends, fear not. If you enjoy the sweet freedom of RESTful urls, I’m here to help. Since this is all built on top of WSGI, we can create a some new Middleware to sit before the application to resolve this little issue.
Read the rest of this entry »
I desperately want to use edge rails to have all the goodies of Rails 1.2, especially the RESTful stuff. The problem is that it’s bleeding edge and I am working on a project that will be public and not for my own desires.
There is a simply_restful plugin available, which is what Rails 1.2 will be modeled after. The problem is that there will be differences between the plugin and the rails source. That means after using one, I have to refactor some code to include conventions like change my delete methods to destroy and some pluralizing stuff as well.
That’s where the simply_restful_backport plugin comes in. The author has made a plugin which implements the RESTful stuff as it will be in Rails 1.2. I am going to try it out this weekend and see how she fits.