I've never liked the options available when implementing multi-page wizards in a web app, especially if you want to let people use the back button. Storing state in the HTTP session takes up memory on the server and makes the session less portable. Encoding state in a cookie is nasty and limits you to a pretty small amount of data.
The Gears Database API seems like a great way to solve this problem cleanly! Store and load the state data on the client's machine in a non-hacky way and keep state out of the session. You could probably even allow the user to leave the page and then later resume where they left off. Has anyone done this yet? Any suggestions? I might take a stab at it, but it could take me a while, since I'm a Gears newbie. Thanks, Matt
