In this post I would like to share with you a very common pattern used in web application development and how I implemented the pattern in my Grails application. Let’s start with a simple explanation of the pattern and what is it useful for.
Post-Redirect-Get
Post-Redirect-Get refers to the flow or process that web applications follow. When user submits the form in the browser the information is typically send with HTTP POST method to a web server. Application processes the information and sends back the response. Response is sent in a form of redirect to another view. Browser loads new state from web server using GET method.
Some of the benefits of using this patterns are:
- Pressing refresh button in the browser will not cause duplicate form submission. The most annoying dialog box asking you if you want to resubmit your form will be gone.
- Bookmarking result page would be possible.
- Pages with forms submissions will be gone from your browser history.
- Nice and clean separation of the HTTP methods that change state of an object (POST, UPDATE, DELETE) from non-destructive, read-only methods (GET).
- Easier to test response, as all you need to check is the redirection. Typically when form is submitted successfully it will redirect to different page then failed submission. To test the behavior it is enough to test the redirection.
With the pattern in mind and the benefits let us try to look at the concrete FooBar example.
Grails example
I assume you know what Grails is. I’ve created a project and created domain object called Foo. The only property it has is a String, Bar that cannot be blank.
package post.redirect.pattern
class Foo {
String bar
static constraints = {
bar blank: false
}
}
Foo controller with two methods responsible for creation of new object.
class FooController {
…
def create() {
def instance = new Foo(params)
if (flash.model){
instance = flash.model
}
[fooInstance: instance]
}
def save() {
def fooInstance = new Foo(params)
if (!fooInstance.save(flush: true)) {
flash.model = fooInstance
redirect(action: "create")
return
}
flash.message = "Hooray, you did it!"
redirect(action: "show", id: fooInstance.id)
}
…
}
When user submits the form and the object is invalid, the browser is redirected back to the form instead of rendering the form with error messages.
There is an extra check to see if user arrived on this page after unsuccessful form submission.
I used flash to store invalid object between pages, so the user could get feedback on what is wrong with provided values.
If you want to try on another example, the easiest way is to create a domain class and generate the scaffolding for it. You can try the browser behavior on generated code.Try refreshing the page after form submission (valid and invalid), try to navigate between pages using Back and Forwards buttons of your browser, try to bookmark the submitted page.
Later, go and modify the code, replace renders with redirects and see browser behavior after that.
Summary
This is all there is to it. It’s rather simple and easy to follow pattern with number of benefits. Grails makes it a doodle to implements,. Have fun redirecting.
Greg
Not too long ago I had a conversation with one of the senior member of the management team of project I’m working on. I had some ideas on how can we do things faster by improving our testing (not developer testing but end-to-end, QA and regression testing). After few minutes of conversation I was asked a very basic question: “What is the definition of DONE on our project?” I was just going to open my mouth and jump out with an answer like: “Well, it takes us usually 3 days to develop piece of functionality”, but I stopped. I actually wasn’t sure. We spend few more minutes discussing some other issues but when I left I felt that this question is still on the back of my mind, trying to desperately find the answer.
Greg Gigon's wEbLOG 