Do we want to follow Post-Redirect-Get?

[cdepillabout]

Do we want to follow the Post-Redirect-Get design pattern?

It looks like PR #42 (https://github.com/blueimpact/kucipong/pull/42/files#diff-f84a648380f9d597ebfd8de3de10fb22R67) returns an html page from a POST handler instead of a redirect.

In order to both (1) follow the Post-Redirect-Get pattern, and (2) send info/error messages back to the user, we would need some sort of messaging system like used in Yesod:

http://www.yesodweb.com/book/sessions#sessions_messages https://hackage.haskell.org/package/yesod-core-1.4.24/docs/Yesod-Core-Handler.html#g:21

Post-Redirect-Get Pros:

• Users are able to use the "back" button in their browser, as well as bookmark any page.
• On the backend, using some sort of message functionality may be easier than using the messages and errors parameters for the templates.

Post-Redirect-Get Cons:

• I think the frontend would have to use some javascript to get the messages out of the session.
• We would have to change the current messages and errors parameters for templates.

@arowM What do you think?

[arowM]

@cdepillabout From the view point of a project manager of this project, I do not propose to introduce Post-Redirect-Get design pattern with extra costs.

However it's also good choice to use this design pattern because we can contribute to the web development flow using Haskell, and of course it seems to be interesting. The Yesod is good framework but it is monolithic and less freedom to choose any library we want. We should provide alternative way to construct a web system with particular purpose libraries.

How do you feel if we set this issue as low priority and solve this after whole system works well with conventional design?

[cdepillabout]

How do you feel if we set this issue as low priority and solve this after whole system works well with conventional design?

That sounds good to me!