Re: gzip/mod_deflate - only works with responses, not requests

> > Are you sure you need mod_deflate;  I believe SOPE compresses its own
> > responses.  Hence the "WODontZipResponse" default.
> You're right.

Have your tried setting "WODontZipResponse" and using mod_deflate?
Then you should just leave the compression to the apache module and keep
SOPE out of the loop (maybe?).   I'd be curious if mod_deflate and SOPE
give differing performance.  Would be at least interesting to check.

Are you going through any HTTP proxy servers?  I've seen those muck-up
when dealing with compressed and uncompressed data.

> > But this only compresses responses.  I've never checked or tested
> > compresses requests.  But requests are typically pretty small compared
> > to responses.
> putObject can be quite chunky. And that can seem quite slow over an ADSL 
> link. 

Understood.

Although other than for things like documents the putObject request
shouldn't be too bad.  Your client binding should, optimally, drop the
log entries and possibly other irrelevant data.

> I'm coming to the conclusion that the problem may well lie with Apache. My 
> searches seem to indicate that mod_deflate gets little usage when it comes 
> to input rather than output.  For now, I will just live with the delay and 
> bring this up on the Apache lists.



-- 
OpenGroupware.org Users
[email protected]
http://mail.opengroupware.org/mailman/listinfo/users