In <[EMAIL PROTECTED]>, on 03/21/03 at 12:53 AM, James A Baker <[EMAIL PROTECTED]> said:
>On Thursday, Mar 20, 2003, at 20:34 US/Central, [EMAIL PROTECTED] wrote: >> - less risk of losing a 'reply' draft if you are a slow typist or take >> a >> phone call only to have your connection timed out (link it to the >> system >> editor for composition instead of using the built-in?, OR >> automatically do >> 'keep alive' in certain modes, OR ... suggestions that keep security >> up >> and aggravation down??). >Just one of the points, and no guarantee this is feasible, but I think I >can make a _suggestion_ for fixing it... >This could (I suspect, but that's without *ever* having looked at the >HTML source of the form, nor sqwebmail in general) probably be set up >VERY easily with a simple time-out JavaScript function on the editing >form's page. There's surely a "Save as Draft" action which I would >presume can be triggered by such a JS time-out function. -- Then simply >have an extra parameter passed to whatever "result page" is the target >of the time-out, so that it knows to tell the user "the draft message >has been saved... you can find it in your <<drafts>> folder." >Alternatively, it could submit the editing form back to itself (keeping >the session active, and the data alive with "minimal" user interruption) >after a JS time out... that is, if it's a matter of the server-based >session being timed out *while* you're still working on data which >concerns you. That would however initiate an infinitely-looping, >never-dying, persistent user session if a browser window was merely left >open inadvertently. -- So, maybe there would have to be a maximum number >of "auto-reloads" to keep that out of the equation. Or maybe it could >check the length of the auto-reloaded data and compare it to the >previous length (stored in a separate form/JS field) and "Save as Draft" >if 2 or 3 subsequent "auto-reloads" had the same exact length... and >were therefore (presumably) caused by a session being left unattended. >Hmm... >... Just some thoughts. Any comments? >-jab Something can surely be done. While it is a simple setting in Squirrelmail, it *does* leave you with a session that can run indefinitely. Surely a hazard on a Cyber-Cafe machine if you have motored off w/o closing it.... Several of your suggestions are more attractive than that.... Bill Hacker ------------------------------------------------------- This SF.net email is sponsored by:Crypto Challenge is now open! Get cracking and register here for some mind boggling fun and the chance of winning an Apple iPod: http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en _______________________________________________ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
