OptimalScuttering
From FOAF
Contents |
[edit] Thoughts on how to Scutter optimally with HTTP/1.1
[edit] Obey HTTP/1.1 14.9 Cache-Control directives
* http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.9
FOAF authors SHOULD serve their content with relatively lengthy Cache-Control directives - ranging into the weeks to months period. This would enabled services to decide when and when not to re-spider your content, relieving load greatly on services.
Scutters and any other caching mechanisms MUST obey these directives otherwise they don't grok HTTP/1.1.
Use of the cache-response-directive can assert privacy and MUST be obeyed by scutters.
Scutters should send max-age, min-fresh or max-stale requests to services which perform caching and re-smushing: ie Plink. Such requests should act as "ping" requests to services like Plink.
only-if-cached directives should be considered for merely updating information, rather than autodiscovery.
Services and communities such as LiveJournal/Plink/etc should take note of http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.9.6
[edit] How can 14.20 Expect be used?
* http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.20
[edit] 14.21 Expires should be used by services where possible
* http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.21
[edit] Is your scutter going to break things?
* http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.22
From: email@foobar.org is useful
[edit] Conditional content
* http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.24 * http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.25 * http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.26 * http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.28
Don't spider it if you don't have to.
[edit] 14.36 Referer
* http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.24
Mention your links! These can be aggregated themselves in server based logs and presented as backlinks -> these resources mention my foaf/rdf :P
[edit] 14.37 Retry After
* http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.37
Avoid missing out on data thats currently down.
[edit] 14.42 Upgrade
* http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.42
Understand other protocols apart from HTTP? Don't forget to tell the server
[edit] 14.46 Warning
* http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.46
Log these for human review later!
