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.
- James Toru Marumoto wrote: >[snip] > I was thinking more like a using "Range: Header" in the PaceSliceAndDice3. > > Ok, here is the situation. I have developed a blog client a couple years > ago, and now kind of popular here in Japan. It's got a couple of thousands > (or more) users. [end of shameless plug] > The requests I get most these days are sync'ing and moving. I get these > requests from the users almost twice in a week. > > People use a blog client at work *and* at home. Naturally, they want Sync'ing > feature since no one wants to override he/she just wrote a while ago at > different PC. It's not good idea to retrive all entries and go through them > everytime a user launch a client application. > So, I think sync'ing is a very impotant feature. > >
