hc-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Oleg Kalnichevski <ol...@apache.org>
Subject Re: HTTP client caching
Date Wed, 25 Jun 2003 20:18:20 GMT
Christian,

Let me present my take on these issues (See below):

On Wed, 2003-06-25 at 21:22, Christian Sell wrote:
> hello all,
> 
> 
> I am looking for a library to implement browser-like behavior, including 
> HTTP 1.1 conformat caching. I have 2 questions regarding HttpClient:
> 
> 1. Has it ever been considered to implement this as part of HttpClient?
> 

Yes, it has and the idea has been turned down, if my memory does not
fail me. The consensus was that HttpClient should remain a HTTP
communication library and would not attempt to evolve into a browser of
a sort, a vacuum cleaner, or anything else. 

> 2. I have seen an archiecture in JTidy (w3c.org), which I find quite 
> handy. They have something called filters that can be registered into 
> the request/respose flow and alter or amend it as needed. Consequently, 
> they have implemented caching as a filter that returns the cached 
> response if applicable.
> I checked into HttpClient and found it almost impossible to introduce 
> something similar - i.e. intercept the request/response flow, without 
> directly hacking into the code. Am I missing something here, or is 
> caching really not in the scope of HttpClient. Would it not make sense 
> to introduce a concept like filters/interceptors (well, not in 2.0 I 
> assume).
> 

That sounds like a good idea for release 3.0. Still, any caching
mechanism should still be out of scope in my opinion. This said, we
happily accept useful code as officially unsupported contributions.

Cheers

Oleg


Mime
View raw message