Hi Dieter, what could it be? If I execute the same script on my local development machine, everything works fine. If I transfer it to the customer and try it there, it shows the described behavior. Regards Florian Reiser -----Ursprüngliche Nachricht----- Von: Dieter Maurer [mailto:dieter@handshake.de] Gesendet: Mittwoch, 16. Juli 2003 20:38 An: florian.reiser@ra-bc.de Cc: 'Zope-allgemein' Betreff: Re: AW: [Zope] Long running process Florian Reiser wrote at 2003-7-16 07:41 +0200:
I don't think that the not-setting of the session variable is causing the timeout. > Maybe the session variable is not set because of the timeout?
I meant (and think I wrote) that this is highly unlikely: DM: Zope notices a browser timeout only after it has computed DM: the complete response (few exceptions). DM: Therefore, it is highly unlikely that not-setting your DM: variable is caused by a browser timeout.
How can I avoid this?
Almost surely, the problem lies somewhere else... Dieter