Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cocoon-dev@xml.apache.org
Message-ID: <3E3E758A.6000403@apache.org>
Date: Mon, 03 Feb 2003 14:58:34 +0100
From: Stefano Mazzocchi <stefano@apache.org>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
 rv:1.3a) Gecko/20021212
MIME-Version: 1.0
To: cocoon-dev@xml.apache.org
Subject: Re: Compressing output from Cocoon
References: <0b3401c2cb82$c509b550$98172ed5@bartguijt>
In-Reply-To: <0b3401c2cb82$c509b550$98172ed5@bartguijt>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Bart Guijt wrote:
> Hi all,
>  
> I'm interested to see whether the following technique is useful for 
> Cocoon apps as well: compressing requested content if the client 
> supports it. The article at the following link illustrates this best:
>  
> 
>     http://www.servletsuite.com/servlets/compress.htm
>  
> 
> I browsed the Cocoon sources to see whether something like this was 
> already implemented, but apparantly it's not.

And IMO should not!

There are much better ways of doing this compression (thru servlet 
filtering or apache 2.0 module chaining)

> Has anybody used this before? What are your experiences?

I haven't used it myself, but if I had to do it I would use servlet 
filtering instead of patching cocoon. cocoon's concern is to create 
output, http compression is part of the transport so it should be 
somebody else's concern to modify the output to reshape it to improve 
the transport.

-- 
Stefano Mazzocchi                               <stefano@apache.org>
    Pluralitas non est ponenda sine neccesitate [William of Ockham]
--------------------------------------------------------------------


---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org