On Thursday 23 June 2005 19:33, Dieter Maurer - [EMAIL PROTECTED] wrote:
> It has nothing to do with a request timeout!
>
> >So whats the reason that this f***ing browser using HTTP1.0?
>
> Zope understands large parts of HTTP 1.1, among others
> the "Keep-Alive" header, but it is not fully HTTP 1.
Ralph wrote at 2005-6-22 18:46 +0200:
> ...
>MS says:
>
>By default, HTTP 1.1 is enabled in Internet Explorer except when you establish
>an HTTP connection through a proxy server. When HTTP 1.1 is enabled, HTTP
>connections remain open (or persistent) by default until the connection is
>idle for
On Jun 22, 2005, at 1:25 PM, Jonathan wrote:Set up your web page so that it has two frames: the main frame (visable) invokes the long running zope script; and a secondary (hidden) frame uses a _javascript_ routine (running on a timer) which queries a no-op zope script. This should stop your browse
out.
Ugly, but it should work.
Jonathan
- Original Message -
From: "Andrew Langmead" <[EMAIL PROTECTED]>
To: "Ralph" <[EMAIL PROTECTED]>
Cc: "ZopeList List"
Sent: Wednesday, June 22, 2005 1:11 PM
Subject: Re: [Zope] Re: Problem with keep-al
If you really need handle an arbitrary processing time. You might
need to separate the request submission from the processing, and the
processing from the results display.
Roughly the way it would work would be like dropping your laundry off
at the cleaners. You bring in the dirty clothes a
