timeout safeguards

[Ben Collins-Sussman <su...@collab.net>]

Recap :  

  * we recently discovered that mod_deflate is buffering server
    replies entirely, which destroys the streaminess (and scalability)
    of apache/ra_dav.

  * there's a raging debate going on (among apache folk) about *how*
    to make mod_deflate stream data:  should mod_deflate do it
    internally, based on some fixed-buffer size?  or should the 'core'
    apache code be sending 'flush' signals to mod_deflate?

  * meanwhile, if you see your client time-out, the workaround is to
    set 'http-compression = no' in the [global] section of your
    ~/.subversion/servers file.


Here's the problem: even if mod_deflate gets fixed today, we can't
really afford to sit around and wait for the fix to come out in
httpd-2.0.48.    Because svn 0.26 will almost certainly be released
before httpd-2.0.48, Karl and I think it would be good to just turn
off neon compression-support by *default* in HEAD (and thus 0.26).
(After apache is released, we can re-enable it as the default.)

If noone objects, I'll just make libsvn_ra_dav deactivate the neon
compression feature by default, and *only* turn it on if the run-time
config has 'http-compression = yes'.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org