On Wed, Jan 29, 2014 at 10:24 AM, Christopher Schultz < ch...@christopherschultz.net> wrote:
> > Now, as Chris pointed out - it would be great to design your app > > that it saves the intermediate work to a database or some secondary > > store that can be retrieved upon login again. Think "shopping > > cart", you are shopping around, the instance goes down, you need to > > login again, and a nice application would persist shopping cart for > > you, not so nice application would not, so when logged in again - > > the shopping cart would be available or not :) > > Exactly. Our strategy - for those interested - is to include enough > information in each request / form to allow users whose work is > interrupted by a login to resume their workflow (in progress) after an > interrupted session. This has the added benefit of allowing users to > go get a cup of coffee, have their session expire, and pick-up where > they left-off after a quick re-login. +1 just experienced this in an (on-the-job) online training that I'm completing. I started an online training 'session' (in a single browser) hours ago, started multitasking on-the-job, go back to the online training, and scroll down (via wheel on my mouse) a little and read the page, multitask, come back to online training, scroll down (via wheel on my mouse) more and do some more reading, and later after more multitasking, the session was closed (maybe via AJAX), and I have a 404 error in the browser. So, i close the browser, click the URL to begin/resume the online training, and the online training opens in the browser to the very exact position on the page that I was last reading. Now, that is real nice! I don't know what they are doing, but they may have some AJAX method on the client that updates database on server, and database update includes what part/position of the page I last read.
