> Well this is debatable because you effectively change the resource itself > and ought to update its meta-data as well (ie Last-Modified and Etag > values). > > Besides, by not doing so can be even worse because an aggregator would > requests the feed, the server would respond with a 304 and the aggregator > would not even know the count ahs changed in the end. It feels even worse. >
Actually the aggregator could NOT send the If-Modified-Since header of course in that specific case and be safe. But this seems like a bit of an abuse of HTTP to me. - Sylvain
