caching-patch V0.2.1 (Was: Re: caching-patch V0.2.0)

[Waldo Bastian]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Monday 26 August 2002 07:36 am, Tobias Anton wrote:
> On Saturday 24 August 2002 23:10, Waldo Bastian wrote:
> > It assumes that when a document with creation time t_doc_create sets a
> > relative expire time t_doc_expire that the images with a creation time
> > t_img_create should expire on t_img_create+t_doc_expire.
> >
> > I think that's wrong and I think the images should expire on
> > t_doc_create+t_doc_expire.
>
> Imagine a cached image that is referenced from all pages of a web site and
> all pages have a relative expire date.
>
> Browsing around will lead to strange results there, i.e. as long as no page
> is visited twice and the time between two page views is less than the
> (relative) expire time, such an image will never be reloaded.

I find the fact that the expiration date of the document sets the expiration 
date of the images a hack in and of itself. If you want to set the expiration 
date of an image you should do that by sending the correct expiration date in 
the http headers of that image.

But to come back to your problem, isn't that then simply a matter of not 
updating the expiration date of an image when it already has a prevous 
expiration date set?

Cheers,
Waldo
- -- 
bastian at kde.org  |   SuSE Labs KDE Developer  |  bastian at suse.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE9ao8DN4pvrENfboIRAh9hAKCbkU8f9JB9c3+J1IP6IX0DxP9SUgCgpJal
kYFxCBuoO8EfUgTjhygh+D4=
=8efZ
-----END PGP SIGNATURE-----