Workflow for syncing up a client repository

[Simone Chiaretta]

I'm building a client app that syncs with Google Reader and after having understood the basics of getting lists of posts and setting tags I was wondering how to sync my client-side repository with the one online.

Specifically, which is the best way to get updates on what the user read online?

Imagine I use my client and download 100 new items.

I mark a few of them (let's say 7) as read then I quite the app. I still have 93 items.

I open the app again, I ask for all the new items after the last time I synced my app (to avoid downloading again all the old items). And I get 15 new items. Now I have 108 items.

I close the app again.

For some reason I go the google reader online, and I mark 50 items as read.

I go back to the client app: how can I know 50 items have been read if I just ask for the updates to the reading list?

Or should I always use the stream/id to get all the reading list (without using the last updated field) and then purge the local repository from the ids that are in the list anymore?

What do you guys do? What do you recommend?

Thank you

Simone

--
Simone Chiaretta
Microsoft MVP ASP.NET - ASPInsider
Blog: http://codeclimber.net.nz
RSS: http://feeds2.feedburner.com/codeclimber
twitter: @simonech

Any sufficiently advanced technology is indistinguishable from magic
"Life is short, play hard"