Hi,
Oskar Pearson wrote:
> Do something like 'exponential back-off' where you obey the TTL's for
> the page, but keep a CRC or something. When the page is next downloaded,
> and if it is the same then keep a record saying 'keep this object for
> 2x the amount it says to keep it'.
How about storing the Content-MD5, if it exists, and promoting its
use? How about ETags? If the Content-MD5 doesn't exist then
generate it on the fly (though I proposed this a while back and it
comes out a bad idea)
> I know that there is currently no way of keeping state, and that it
> would probably use huge amounts of disk space :)
and RAM if you keep the MD5 in the object info as part of the struct.
Another 16 bytes for a 128-bit checksum.
-- miguel a.l. paraz <map@iphil.net> +63-2-750-2288 iphil communications, makati city, philippines <http://www.iphil.net>Received on Tue Jul 29 2003 - 13:15:42 MDT
This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 16:11:22 MST