Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Jakarta Commons Developers List" <commons-dev@jakarta.apache.org>
Date: Mon, 11 Feb 2002 12:02:45 -0800 (PST)
From: "Craig R. McClanahan" <craigmcc@apache.org>
To: Jakarta Commons Developers List <commons-dev@jakarta.apache.org>
Subject: RE: [PROPOSAL] Decoding multpart mime HTTP POST API
In-Reply-To: <80F5674514B4D311BAFC0040F6A45EEE2435A6@ntserver>
Message-ID: <20020211115913.J91109-100000@icarus.apache.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


On Mon, 11 Feb 2002, Ignacio J. Ortega wrote:

>
> BTW I dont think that commons is suitable for a Filter repository.. we
> are suppossed to be doing components, is a 2.3 filter a component? i
> dont think so..
>

In the Tomcat 4 distribution, there's a couple of filters included in the
example webapp:

* Set the character encoding of an input request if the
  browser didn't send it

* Transparently do compression on the response if the
  browser says it can handle a compressed response

Both of them are small, stand-alone, and generally useful -- but they are
difficult to get at being buried inside a webapp.  I don't know about you,
but that sort of fits my notion of a "component" :-).

I agree that, in a longer term, a jakarta-filters project (like
jakarta-taglibs) would be a good idea.  We need to jump-start the content
and the community a little bit first, though, and the responses so far to
Glenn's proposal seem to indicate some interest.  The sandbox would be a
reasonable place to get started.

>
> Saludos ,
> Ignacio J. Ortega
>
>

Craig


--
To unsubscribe, e-mail:   <mailto:commons-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:commons-dev-help@jakarta.apache.org>