CSC/ECE 517 Fall 2009/wiki2 3 pp: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 3: | Line 3: | ||
=<font color="windowtext">Double Submit Problem</font>= | =<font color="windowtext">Double Submit Problem</font>= | ||
What is the requirement of having this pattern. Some examples such as Add to cart being pressed twice can result in 2 items in the cart etc. The example should provide or demonstrate how devastating this can be. Some financial example such as clicking on Pay button twice could charge credit card twice etc. | |||
=<font color="windowtext">Solutions for Double Submit Problem</font>= | =<font color="windowtext">Solutions for Double Submit Problem</font>= | ||
Revision as of 05:31, 7 October 2009
Synchronizer Token Pattern - Introduction
Double Submit Problem
What is the requirement of having this pattern. Some examples such as Add to cart being pressed twice can result in 2 items in the cart etc. The example should provide or demonstrate how devastating this can be. Some financial example such as clicking on Pay button twice could charge credit card twice etc.
Solutions for Double Submit Problem
Can be server side or client side. Server Vs Client which one is better?
Client Side Solution - Javascript Control Disabling
Briefly describe the approach. Discuss pros and cons.
POST-REDIRECT-GET
Briefly describe the approach. Discuss pros and cons.
Synchronizer Token Pattern
How the patten works? Diagrammatic Representation? Theoretical View? Reply on session.
Implementations of the pattern provided by various frameworks
Struts
Spring Web Flow
Ruby on the Rails
Grails
References
[1] References go here