0

What is the current reasoning for the badge routes not being paged? Badges (/tags) is probably the current longest route, and it is annoying that this route isn't paginated, but stackauth/sites is. Should it not be the other way around (unless I am missing something obvious)?

Improve this question

1 Answer 1

Reset to default
1

They were't paginated due to their essentially static nature.

This has since been determined to be a mistake, they're slated to be redone in a subsequent API version.

Improve this answer
3
  • great, something to look forward to recoding :/ And the sites method isn't [roughly] equally static?
    – Jonathan.
    Commented Mar 15, 2011 at 0:08
  • @Jonathan: The sites method is obviously not static by nature (in the sense that it changes frequently).
    – Nathan Osman
    Commented Mar 20, 2011 at 6:44
  • 1
    Sites route is quite static, we are told it must be called no more than once a day at minimum, and compared to questions it's very static. But there is no case when you'd only download the first page of sites.
    – Jonathan.
    Commented Mar 20, 2011 at 9:20

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .