Tumblr API "limit" argument should default to maximum if set too high

[Daniel Jalkut]

Hi - a couple things:

1. The API Documentation is out of date with respect to the "limit" argument. It says it accepts a value from 1-20 but testing indicates it accepts a value from 1-50.

2. If the specified value is higher than 50, it defaults to 20. It would be more in the spirit of satisfying the API client's intention to default to 50, or more generally, to default to whatever the maximum is given a value that exceeds that maximum.

The practical applicability here is in my app MarsEdit, which supports a user-facing setting for controlling how many posts to fetch in each request. Setting a higher "limit" value makes a lot of sense for blogs that have hundreds and hundreds of posts, so that the entire archive of posts can be downloaded in only a few requests, instead of dozens.

A user with a particularly large number of posts might get eager and set the limit value to 100 or higher, hoping to get things downloaded more efficiently. Unfortunately the way things are currently set up, they'll end up with a less efficient download as the API defaults to 20 at a time.

Daniel

[Michael Ceyko]

Hey Daniel,

Thank you for your input.

This is a good idea. I don't see any reason why we shouldn't do this, so I'm filing a ticket internally for it to be changed.

Regards,

Mike

[Daniel Jalkut]

Thanks, Michael!