Re: [Phpwiki-talk] edit timeout duration

[Reini U. <ru...@x-...>]

Whit Blauvelt schrieb:
> On Thu, Mar 25, 2004 at 07:03:25PM +0100, Reini Urban wrote:
>>Micki Kaufman schrieb:
>>>Just wondering - where can I affect the duration after which an edit
>>>times out?
>>>
>>>One of my team considers it 'an issue', since she remained in edit mode 
>>>for a long time, without saving, and then lost her work. I'd like to 
>>>understand what's possible to manage the complaint.
> 
> 
>>most likely it's the server-specific php max_execution_time. (typically 30
>>seconds per request).
> 
> So the suggestion is that it wasn't being in "edit mode" but that what she
> had edited took more than 30 seconds to process once it was submitted? 
> 
> Is this then a "gotcha" for particularly long pages? Something that will be
> run into if a page is the equivalent of a book chapter in length? Just
> wondering since my prospective use will involve some long pages.

Ah, I understand now!
It could also be a session.timeout thing, which usually happens in 
webmail applications, when people spend too much time in the editbox and 
loose their session data and therefore their authlevel and userid then, 
when finally saving.

You can either set ALLOW_ANON_EDIT (hackish workaround) or you have to 
enlarge the session timeout in php.ini
At my ISP we use 20 minutes php session timeout for such kind of users.

This will either blow up your tmp directory if sessions are filebased 
(no major problems on reiserfs, but major problems on ext or ntfs 
filesystems and a lot of php users).
Or on DB_SESSION and a heap table it will lead to RAM shortage, but 
makes no harm on normal table types. it's just almost as slow as file 
based session.
There exists a better php session modules for larger ISP's
-- 
Reini Urban
http://xarch.tu-graz.ac.at/home/rurban/