You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hc.apache.org by Ortwin Glück <or...@nose.ch> on 2005/01/17 09:57:46 UTC
HCLA: Filters
In our architecture draft at
http://wiki.apache.org/jakarta-httpclient/HttpClientApiRedesign
is HttpFilter meant to be a filter on the HTTP headers only?
Or will it be possible to filter a HTTP entity, too?
Should we provide two distinct interfaces, like:
HttpHeaderFilter
HttpEntityFilter
maybe?
Ortwin Glück
--
_________________________________________________________________
NOSE applied intelligence ag
ortwin glück [www] http://www.nose.ch
software engineer
hardturmstrasse 171 [pgp id] 0x81CF3416
8005 zürich [office] +41-1-277 57 35
switzerland [fax] +41-1-277 57 12
---------------------------------------------------------------------
To unsubscribe, e-mail: httpclient-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: httpclient-dev-help@jakarta.apache.org
Re: HCLA: Filters
Posted by Ortwin Glück <or...@nose.ch>.
Oleg Kalnichevski wrote:
> Odi,
>
> I am convinced content filtering should be possible too. One should be
> able to plug in Gzip content filter without having to subclass any of
> the standard HttpRequest or HttpResponse classes. However, I do not
> think one can meaningfully manipulate complex content without having
> access to the headers, so I do not think providing separate interfaces
> for headers and content filtering brings too much value.
>
> Oleg
We will see when we get our hands dirty...
---------------------------------------------------------------------
To unsubscribe, e-mail: httpclient-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: httpclient-dev-help@jakarta.apache.org
Re: HCLA: Filters
Posted by Oleg Kalnichevski <ol...@apache.org>.
On Mon, Jan 17, 2005 at 09:57:46AM +0100, Ortwin Gl?ck wrote:
> In our architecture draft at
> http://wiki.apache.org/jakarta-httpclient/HttpClientApiRedesign
>
> is HttpFilter meant to be a filter on the HTTP headers only?
> Or will it be possible to filter a HTTP entity, too?
>
> Should we provide two distinct interfaces, like:
> HttpHeaderFilter
> HttpEntityFilter
> maybe?
>
> Ortwin Gl?ck
>
Odi,
I am convinced content filtering should be possible too. One should be
able to plug in Gzip content filter without having to subclass any of
the standard HttpRequest or HttpResponse classes. However, I do not
think one can meaningfully manipulate complex content without having
access to the headers, so I do not think providing separate interfaces
for headers and content filtering brings too much value.
Oleg
---------------------------------------------------------------------
To unsubscribe, e-mail: httpclient-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: httpclient-dev-help@jakarta.apache.org