API Modification: add 'update_before' and 'update_after' to reviews.list

[Grunthos]

Background

In synchronizing books with goodreads, I retrieve books in reverse update date and stop when I get to my last known update date. This is fine, but if a network outage occurs, I need to restart from the beginning.

Solution

Add 'update_after' as a parameter to reviews.list and retrieve them in ascending update date.

If this were available, then I could update my 'last goodreads date' after each row, and a restart would be able to pick up exactly where the last job failed.

Why is this good?

Less API calls, less network traffic.

Why have update_before?

Completeness. I like symmetry. Someone will probably ask for it.

[Michael]

Hmmm, we have a year filter would you want to use that?

[Grunthos]

It would help when there are many reviews spread across multiple years, but the main objective is to get reviews that were changed in the last few days or so.

[Michael]

the param is "read_at" this won't work if the use didn't specify when the book was read unfortunately.

http://www.goodreads.com/review/list/...