> -----Original Message-----
> From: Robin Berjon [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, November 15, 2000 12:19 PM
> To: Geoffrey Young
> Cc: '[EMAIL PROTECTED]'
> Subject: RE: [RFC] Apache::Expires
>
>
> At 11:17 15/11/2000 -0500, Geoffrey Young wrote:
> >> easy to get mixed up in the details. I think Andreas wrote
> >> something about
> >> all those issues last year, but I can't track it down right now.
> >
> >I think he wrote the section in the guide on headers - that
> will definitely
> >help sort things out...
>
> Ah, yes, in a place that obvious I had no chance of finding it ;)
>
> >say you want to cache a dynamic document for a week from
> creation - how do
> >you define when the week started?
>
> You mean if say, on tuesday a document is generated and says
> it will expire
> in a week, if it is rerequested on friday it will still need to say it
> expires the following tuesday right ?
something like that... for instance, using mod_expires you can specify a
one week from modification time for expiration. that's more difficult to do
with dynamic stuff since you don't have a start point (the 'document' is
modified on every access).
I was thinking that to specify a one week expiration date would set the
Expires header (or Last-Modified or whatever) to "last monday + one week".
documents created on friday only really get 3 days instead of a week, but...
similarly for months, years, days, etc...
you loose true granularity of control (?) but gain some sort of caching this
way. I dunno...
> That would require persistence,
> probably a db or dbm.
yeah, except that I suspect the overhead of that would be just as bad as the
processing to create the document in the first place...
--Geoff
>
> -- robin b.
> I don't suffer from insanity. I enjoy every minute of it.
>