Are you proposing that something publishing a feed keep track of what entries were in previous versions? As in, feed X retrieved just now, contains entries a,b,c and feed Y was published last containing d,e,f.
What sort of headers are you suggesting for providing info on uninformed requests? That is, from an aggregator that's never tried connecting before and doesn't have any previous knowledge of the feed? This being how most RSS aggregators behave currently. While I find the idea of tracking previous instances interesting I'm not sure how many content sources are going to capable, let alone interested, in doing so. I'd be more inclined to want semantics on what kinds of ranges a source can provide. Be they date, numeric index or other forms. As, informing the aggregator the source provides date range bounding, dns-like serial number increments, last ETag or whatever. But tracking what was the "previous" feed seems unlikely when something like a dynamic script source is being used. There is no "previous" instance only what the script detected as 'relevant' items at that time. -Bill Kearney ----- Original Message ----- From: "Mark Nottingham" <[EMAIL PROTECTED]> > I've made a proposal to fill in the "Managing Feed State" section; > comments / suggestions appreciated. > http://www.intertwingly.net/wiki/pie/PaceFeedState
