--On August 9, 2005 9:28:52 AM -0700 James M Snell <[EMAIL PROTECTED]> wrote:
>> I made some proposals for cache control info (expires and max-age). >> That might work for this. >> > I missed these proposals. I've been giving some thought to an <expires /> > and <max-age /> extension myself and was getting ready to write up a draft. > Expires is a simple date construct specifying the exact moment (inclusive) > that the entry/feed expires. Max-age is a non negative integer specifying > the number of miliseconds (inclusive) from the moment specified by > atom:updated when then entry/feed expires. The two cannot appear together > within a single entry/feed and follows the same basic rules as atom:author elements. Here it is: <http://www.intertwingly.net/wiki/pie/PaceCaching> Adding max-age also means defining IntegerConstruct and disallowing white space around it. Formerly, it was OK as a text construct, but the white space issues change that. Also, we should decide whether cache information is part of the signature. I can see arguments either way. wunder -- Walter Underwood Principal Architect, Verity
