Timeline for Prefered way to retrieve all search results
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 26, 2011 at 19:58 | comment | added | Gilles 'SO- stop being evil' |
See the question: if there's a deleted result, it's counted in the 100. I guess deleted results are eliminated late in the chain. I thought …/page=2 just after …/page=1 was counted differently, but I can't find a reference to that now, I might have imagined it or confused with some other site's API.
|
|
| Oct 26, 2011 at 19:50 | comment | added | Nathan Osman | Good point with the ">100 with the same timestamp" problem though. I hadn't thought of that. | |
| Oct 26, 2011 at 19:49 | comment | added | Nathan Osman | @Gilles: It doesn't count as a separate request when you're fetching more than one page? ...and why would there by fewer than 100 results on anything but the last page? | |
| Oct 26, 2011 at 19:28 | comment | added | Gilles 'SO- stop being evil' | Ok, this technique works to avoid skipping an item in the middle. It assumes there aren't 100 questions with the same date (this is unlikely to happen naturally, but what about a mass import?). Your termination condition is wrong, there can be less than 100 results at any time. This technique is rather costly; as I understand it, querying page=2 after page=1 is cheaper in the backend (because the data is already sitting in some cache, I guess), and from the user's point of view it's cheaper because it doesn't count as a separate request against the API usage quota. | |
| Oct 26, 2011 at 3:05 | history | answered | Nathan Osman | CC BY-SA 3.0 |