2006/3/23, James M Snell <[EMAIL PROTECTED]>:
>
> One approach that I've taken in our server implementation is to use
> Last-Modified / If-Modified-Since HTTP headers to provide a kind of
> sync'ing mechanism. Specifically, when a client requests the APP feed
> using a If-Modified-Since header, the server will return ONLY those
> entries that have been modified since the specified date. If no entries
> have been modified, the client will receive the expected 304 Not
> Modified status response.
Hmm, not sure this is not an abuse of those headers…
The "If-Modified-Since" section of HTTP/1.1 reads:
b) If the variant has been modified since the If-Modified-Since
date, the response is exactly the same as for a normal GET.
If it had been that simple easy, there wouldn't have been a need for
RFC3229/feed ;-)
I would however also consider an abuse (or misuse) of RFC3229/feed to
base the delta on a "last-modified" property while sorting the feed by
"atom:updated"…
RFC3229/feed was born here:
http://bobwyman.pubsub.com/main/2004/09/using_rfc3229_w.html
--
Thomas Broyer
