The real question here is what web2py can/could do about people landing on unexpected pages, which then go to login. A form submission on a web2py restart, loss of cookie, browser restart, session timeout, etc could, in theory, be preserved (the login page should redirect/ resubmit to the original page). Lost edits are just a special case of this.
In this specific case, again, as an idea, the editor actually could do server assisted autosaves: just save the document in a temp admin table or file, probably through some AJAX magic to make it transparent to the user. In either case, it would be a serious mod to both web2py and the editor itself, which is just a borrowed component in web2py. On Oct 23, 9:00 am, Keith Edmunds <[EMAIL PROTECTED]> wrote: > On Wed, 22 Oct 2008 23:12:24 -0700 (PDT), [EMAIL PROTECTED] said: > > > This is one reason > > why many people don't trust web editors -- they are too prone to lose > > work. > > Whilst I agree with the basic point you make about somehow saving the > context of the editing if possible, if you don't trust web editors then > why are you using one?? None of my web2py editing is done via the web > interface for a number of reasons, not least of which is that there is no > recovery journal. > > Keith --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py Web Framework" group. To post to this group, send email to web2py@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
