Hi,
I am not sure what is causing the issue but I will investigate for you. In the meantime please know that Twitter is now in version 1.1 and the documentation you referenced in for version 1.0.
The agent does not seem to affect the rate limit anymore.
What could happen though is if you are using search and you set the MaximumNumberOfResult parameter > 100.
The reason is that Twitter limit a search result set to 100. Consequently Tweetinvi will execute multiple request so that it returns the number of result you are looking for.
Also, please not that making a MaximumNumberOfResult of 200 does not imply it will result in only 2 queries.
The reason is that Twitter Search API does not always return sets of 100 results event if more than 100 results are available from the API.
Consequently a limit to 200 will result in a minimum of 2 queries but will often result in 3 to 4 queries.
Please let me know if this help.
Linvi
I am not sure what is causing the issue but I will investigate for you. In the meantime please know that Twitter is now in version 1.1 and the documentation you referenced in for version 1.0.
The agent does not seem to affect the rate limit anymore.
What could happen though is if you are using search and you set the MaximumNumberOfResult parameter > 100.
The reason is that Twitter limit a search result set to 100. Consequently Tweetinvi will execute multiple request so that it returns the number of result you are looking for.
Also, please not that making a MaximumNumberOfResult of 200 does not imply it will result in only 2 queries.
The reason is that Twitter Search API does not always return sets of 100 results event if more than 100 results are available from the API.
Consequently a limit to 200 will result in a minimum of 2 queries but will often result in 3 to 4 queries.
Please let me know if this help.
Linvi