--- On Fri, 5/14/10, Christoph Zwerschke <cito@...> wrote:
> From: Christoph Zwerschke <cito@...>
> Subject: Re: [Webware-discuss] self.response().flush() on 1.1b1 with WSGI
> To: "Discussion of Webware for Python including feedback and proposals." <webware-discuss@...>
> Date: Friday, May 14, 2010, 1:14 PM
> Am 14.05.2010 20:26 schrieb Roger
> > I use a call to self.response().flush() on a couple of
> long running
> > transactions. With the WSGI adapter on 1.1.b1
> the transaction runs
> > to completion, but nothing is transferred until the
> > completes.
> > I haven't tested this with other adapters.
> Anyone else notice this?
> Just tested it with mod_webkit, mod_scgi and mod_wsgi and
> it worked
> nicely with all of them.
> Are you sure you're using the adapter? It does not work
> with the
> built-in webserver. Also, some Firefox plugins tend to pile
> up response
> data. Did you test with different browsers?
> There have been some changes to the WSGI adapter after
> 1.1b1, you can
> try with the current version (but it should also work with
> -- Christoph
I am bringing up a new server with Ubuntu 10.04. The problem was that Apache now comes with mod_deflate on by default and mod_deflate waits for and compresses the entire transaction's output before sending it on.
For the benefit of anyone else who is using flush on a few long running transactions, mod_deflate can be turned off for a single servlet by adding a line to the apache conf:
SetEnvIf Request_URI ^/webkit/MyXaction no-gzip=1
Thanks for all your help on the Webware enhancements Christoph!