Document how hubs and publishers SHOULD use etags, last-modified, and other caching headers

Tallefer / pubsubhubbub

Automatically exported from code.google.com/p/pubsubhubbub

Other

0 stars 0 forks source link

Document how hubs and publishers SHOULD use etags, last-modified, and other caching headers #37

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago

SUMMARY:

Right now it's a good idea for hubs to do this, but let's make it even more
clear in the spec.

RELEVANT SECTION: 7.2

COMMENT/REQUEST:

See detail for reasons in
http://code.google.com/p/pubsubhubbub/wiki/PublisherEfficiency#Atom_feed_windowi
ng

Original issue reported on code.google.com by bslatkin on 20 Jul 2009 at 10:18

GoogleCodeExporter commented 9 years ago

Original comment by bslatkin on 9 Feb 2010 at 3:20

Added labels: spec0.3

GoogleCodeExporter commented 9 years ago

Addressed in 0.3 draft spec

Original comment by bslatkin on 9 Feb 2010 at 6:05

Changed state: Fixed