System: Umbraco Version - 4.7.1 ,Windows Server 2008 – 8gb memory – 4 Zeon 2.27Ghz processors service pack 1 – 64 bit OS , IIS version 7.5.7600.16385, SQL Server 2008 R2, Stacktrace - N/A
On a multi-page contour form, after the user presses next, the data is saved in memory on the server. When the user returns using the same browser, the cookie retrives the data form memory and repopulates the earlier pages in the form w/the previously entered data. See below.
However, if the server has to be restarted, the data in memory is gone and no longer available to the user.
We would change the session state to StateServer or SQLserver, but then every session state, not just Contour would invoke this process potentially slowing the system down. See below.
Would using "partial submission" in the workflow get around this issue? If so how does that implemented? Is there a submit or save button on each page?
Partial Submission of Form vs. Session State
System: Umbraco Version - 4.7.1 ,Windows Server 2008 – 8gb memory – 4 Zeon 2.27Ghz processors service pack 1 – 64 bit OS , IIS version 7.5.7600.16385, SQL Server 2008 R2, Stacktrace - N/A
On a multi-page contour form, after the user presses next, the data is saved in memory on the server. When the user returns using the same browser, the cookie retrives the data form memory and repopulates the earlier pages in the form w/the previously entered data. See below.
However, if the server has to be restarted, the data in memory is gone and no longer available to the user.
We would change the session state to StateServer or SQLserver, but then every session state, not just Contour would invoke this process potentially slowing the system down. See below.
Would using "partial submission" in the workflow get around this issue? If so how does that implemented? Is there a submit or save button on each page?
Here's the answer - I was able to find it w/a bit of digging.
Thanks to the legions of people that responded!
is working on a reply...