Hi Travis,
Ok, so I fixed the slow processing and now its going too fast and hitting the limits.
I can see the below values ok however can you clarify the reset value
X-RateLimit-Limit X-RateLimit-Remaining X-RateLimit-Reset
The number I get from the X-RateLimit-Reset when X-RateLimit-Remaining is 0 is 1449428071
What is this, is this the total time in seconds , milliseconds etc I must wait before I can start making requests again?
this is a rather large number and even in milliseconds would come to quite a long time
找不到电影或节目?登录并创建它吧。
Kevin Deery 的回复
于 2015 年 12 月 07 日 5:57下午
Thank you for the info, its funny that I heard only a few days ago that unix servers have a beginning of time as 1970 and here I am hearing it again today lol
I'm new to api limits and I'm trying to find a means of handling the limits in c#
can seem to find any examples on best approach on the net :(
Kevin Deery 的回复
于 2015 年 12 月 15 日 6:41上午
I have resolved this issue for now,
I put a small 2.5 millisecond delay into the calls and it never hits the limit, just process 1107 movies in 32 mins, at this point I don't know it this is good because ive no other bench marks to compare against however its a very significant increase from the sequential means of processing a collection.
:)
Kevin Deery 的回复
于 2015 年 12 月 15 日 9:18上午
Thank you, this is exactly what I need. I don't like the delay because its not reliable.
:)