Daniel Jilg wrote:
Second thing: The problem with standard actions. That should be possible
if you dont actually save the data to the database as long as the wizard
is running, but into a session instead. Then, when the user has entered
What on earth is wrong with saving to the database? If you model
correctly you will have a Script and Submitted Script. Why shouldn't a
user be able to come back to a partially completed script tomorrow?
The session system is merely there to provide an illusion of state
between what are actually unconnected HTTP requests to various
webservers. It should really be nothing more than a bunch of pointers
to stuff *stored in the database*.