httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From TOKI...@aol.com
Subject Re: More thoughts on caching in v2.0 - filtering
Date Tue, 22 Aug 2000 12:05:37 GMT

In a message dated 00-08-22 10:05:35 EDT, Graham Leggett writes...

> Caching Using Filters:
> Any comments on this?

Sure.
It's a good idea.

> The caching engine has two specific tasks:
>  
>  - Put data into the cache
>  - Take data out of the cache
>  
> Splitting up the data leaves us with two entities, a filter, and a
> content generator:
> It's as simple as that.

You betcha. Giddyup.

But... about 2 seconds after that someone will want it to 
look like this...

>  - Put data into the cache ( and compress it at the same time )
>  - Take data out of the cache ( and then do the following... )

A. See if the User-Agent meets real-world criteria for accepting
Content-encoding and/or any form of real-time compression.
B. See if the entity requested meets local criteria for being
delivered compressed ( Big enough to bother with, right mime type, 
yada, yada ).
C.Either send the compressed cache goodie back 'as-is' or, ir
compression is not needed or warranted... DECOMPRESS the
cached entity and send it back.

This is a CLASSIC case, then, of a filter needing to probably
install OTHER filters either BEFORE or AFTER itself in 
order for it to work elegantly.

Yours
Kevin Kiley
CTO, Remote Communications, Inc.
http://www.RemoteCommunications.com
http://www.rctp.com - Online Internet Content Compression Server




Mime
View raw message