> Just recently, Marty (cc'd) made an experimental patch to get > compression directly in the http protocol. One reason to do that was > to make it happen after the protocol module has fixed the charset > encoding.
This might be something being handled by a vary_callback to generate the proper matching key? > Another is that it can be tied in with the protocol cache > (it might not be wise to spend cpu on compressing dynamic answers). It might depend on the kind, or amount of data whether or not it is worthwhile compressing a dynamic answer, and depending on the definition of "dynamic". Hooked to the protocol cache it can be more worthwhile to have some small set of dynamically generated data being compressed if it is protocol cached for 1 minute only, while something more compressable is less worthwhile if it is not protocol cached afterwards. I think it can all be done in a filter module, where some hooks at the protocol level might help (but not even sure if necessary). AvS __________________________________________________________ Deze e-mail en de inhoud is vertrouwelijk en uitsluitend bestemd voor de geadresseerde(n). Indien u niet de geadresseerde bent van deze e-mail verzoeken wij u dit direct door te geven aan de verzender door middel van een reply e-mail en de ontvangen e-mail uit uw systemen te verwijderen. Als u geen geadresseerde bent, is het niet toegestaan om kennis te nemen van de inhoud, deze te kopieren, te verspreiden, bekend te maken aan derden noch anderszins te gebruiken. The information contained in this e-mail is confidential and may be legally privileged. It is intended solely for the addressee. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. Please notify us immediately if you have received it in error by reply e-mail and then delete this message from your system. __________________________________________________________
