The invention I was referring to was the Last-Retrieved header. I'm
aware of the RFC3229+feed stuff but I'm very much in favor of the
"Here's the last time I was here" approach rather than the, "Here's some
opaque version tracking token you gave me the last time I was here, use
it to go figure out when I was here last even tho I'd be more than
capable of being able to tell you that myself" approach. Regardless,
either works.
- James
Thomas Broyer wrote:
James M Snell wrote:
Another potential solution (requires a bit of invention) would be to
add a "Last-Retrieved" http header to the GET request. The server
could choose to use the date to tune its response.
GET /collection-uri HTTP/1.1
Host: example.org
Last-Retrieved: Sun, 6 Nov 2005 12:00:00 GMT
RFC3229 w/ feed [1] has the same concept, using ETags instead of dates.
This is not really invention ;-) and I already proposed using it for
syncing.
[1] http://bobwyman.pubsub.com/main/2004/09/using_rfc3229_w.html
