I wouldn't mind a solution with the new tab/jquery popup does the re- login, especially if we make it work with generic forms. Keepalive is not that good as that would make session timeout/expiry pointless (IMO kind of paradoxical to be the same page that sets the timeout to do the keepalive to avoid that very same timeout). Or, as somebody said, just store the complete request object and re-execute it upon successful login.
On Feb 22, 11:32 pm, mdipierro <mdipie...@cs.depaul.edu> wrote: > If you tell me this is the only missing feature I can easily add an > ajax ping to keep alive the session. > > Massimo > > On Feb 22, 4:06 pm, Boris Manojlovic <boris.manojlo...@gmail.com> > wrote: > > > In current form it does not do that :) > > Not in real sense of it, as I still did not fixed "issue" with session > > expiration (it is currently just avoidance of reload - and "loss of code" > > because of re-login process ;)) and as such it is still not a finished > > product :\ > > Will try to see where to patch in check for "from_ajax" in login or exact > > code that check if session is still valid. > > Idea is to always have open editor with maybe "flash" part of screen showing > > up "Session Expired\nEnter Password here: ______", when expired and then be > > able to continue working after login > > So if you don't close browser window it should keep your code safe. > > So that is idea :) > > > On Sun, Feb 22, 2009 at 9:18 PM, mdipierro <mdipie...@cs.depaul.edu> wrote: > > > > Nice patch. Can you explain how does it solve the "loss of code > > > issue"? > > > > Massimo > > > > On Feb 22, 12:16 pm, Boris Manojlovic <boris.manojlo...@gmail.com> > > > wrote: > > > > Hello to All, > > > > > i have started to work on something called "ajax" code editor. > > > > What exactly does it mean? > > > > > 1. No need for reloads on editor page (just think about undo redo in > > > > editor window) > > > > 2. No "terrible loss of code" if you are logged out (application > > > > timeout... with that "great" redirect to login page...) > > > > 3. speed gain > > > > > Current implementation has "save" functionality only and it works just > > > from > > > > firefox (konqueror ignores my jquery code and same for opera...). > > > > Most coding as it would be expected should (and is) done on client side > > > and > > > > will degrade depending if user use javascript at all - no script no ajax > > > > anyway. > > > > All messages in current stage are json passed to client. > > > > Patch against latest SVN from google code > > > > > P.S. Comments welcome and needed (to continue on this idea or not) > > > > -- > > > > "Only two things are infinite, the universe and human stupidity, and I'm > > > not > > > > sure about the former."-Albert Einstein > > > > > ajax_editor.patch > > > > 7KViewDownload > > > -- > > "Only two things are infinite, the universe and human stupidity, and I'm not > > sure about the former."-Albert Einstein --~--~---------~--~----~------------~-------~--~----~ 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 web2py+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
