Re: Possible bug: Got timed out --lost changes to file

Janne Jalkanen wrote:
>> But the best thing to do? You can always refresh the current Edit
>> window while editing as that *shouldn't* lose your changes. Works
>> fine for me anyway (FireFox on Ubuntu linux), you might test that
>> out for your own browser with a simple edit just to be sure.
> 
> I would recommend increasing the default timeout.  Maybe we should put a 
> better timeout in the web.xml we ship with, as this seems to be a FAQ.

Yes, but there's downsides to that as well:

   a. a longer default timeout means the page remains locked on users
      who've abandoned an edit session. For quiet wikis this is probably
      not an issue, more so on busy ones

   b. let's say we set the default timeout at an hour. Anyone who has
      actually been editing for an hour could lose a substantial
      investment, the longer the timeout, the longer the investment.
      One might remember that this thread began on Claudia's two hour
      edit session, a substantial investment of time. But I'd likewise
      not want to set the default timeout that long.

So yes, increase the default timeout but I think documenting the
ability to refresh the edit session from the browser is probably
also a good idea. And also, yes, updating the FAQ.

Murray

...........................................................................
Murray Altheim <murray07 at altheim.com>                           ===  = =
http://www.altheim.com/murray/                                     = =  ===
SGML Grease Monkey, Banjo Player, Wantanabe Zen Monk               = =  = =

       Boundless wind and moon - the eye within eyes,
       Inexhaustible heaven and earth - the light beyond light,
       The willow dark, the flower bright - ten thousand houses,
       Knock at any door - there's one who will respond.
                                       -- The Blue Cliff Record