Autosave vs. Persistent State
So the goal is to have a SQL based state. A tag in a hidden input field registered by the base page will be the unique id to get this state. If it is lost it can be recovered via this tag. So loss of the session has essentially no effect (besides causing a reload from the database).
But in the meantime I feel like I need to have a solution to saving. What I have currently built is an autosave mechanism, that will write out autosave files when your session times out. The question is, is this enough? Probably. It has the same format as a TOC file and the filename can be rewritten and picked up by BBDataManager. Of course, the drawback is that the user has to ask for this.
My original vision (that I have moved beyond) was to allow this autosave to be accessible from the history page. Maybe I should look into that. But it is partially a management decision as to whether the current autosaving mechanism will be sufficient to appease Pearson.
But in the meantime I feel like I need to have a solution to saving. What I have currently built is an autosave mechanism, that will write out autosave files when your session times out. The question is, is this enough? Probably. It has the same format as a TOC file and the filename can be rewritten and picked up by BBDataManager. Of course, the drawback is that the user has to ask for this.
My original vision (that I have moved beyond) was to allow this autosave to be accessible from the history page. Maybe I should look into that. But it is partially a management decision as to whether the current autosaving mechanism will be sufficient to appease Pearson.

0 Comments:
Post a Comment
<< Home