一般来讲,基于REST提供云数据的WEB服务,通常会使用Rate Limit来限制第三方的应用(这里包括桌面应用及其基于WEB的应用)使用该服务频度。
典型的例子是,一个典型的例子是Twitter API, 它的RATE Limit是:
100 API calls /hour/account. 也就是说,如果同一个账户,在一个小时内,调用REST API的次数超过了100,会得到rate limit exceeded错误。
具体请参考:
http://tweetdeck.posterous.com/what-does-rate-limit-exceeded
。
同样的例子,还有delicious REST API(http://delicious.com/help/api), 类似的的规定:两次查询之间的时间间隔至少等一秒钟
(Please wait AT LEAST ONE SECOND between queries, or you are likely to get automatically throttled. If you are releasing a library to access the API, you MUST do this.) 相应的参考文档:
http://support.delicious.com/forum/comments.php?DiscussionID=2205
http://www.nabble.com/API-rate-limit--td15812267.html
http://therning.org/magnus/archives/237
典型的例子是,一个典型的例子是Twitter API, 它的RATE Limit是:
100 API calls /hour/account. 也就是说,如果同一个账户,在一个小时内,调用REST API的次数超过了100,会得到rate limit exceeded错误。
具体请参考:
http://tweetdeck.posterous.com/what-does-rate-limit-exceeded
。
同样的例子,还有delicious REST API(http://delicious.com/help/api), 类似的的规定:两次查询之间的时间间隔至少等一秒钟
(Please wait AT LEAST ONE SECOND between queries, or you are likely to get automatically throttled. If you are releasing a library to access the API, you MUST do this.) 相应的参考文档:
http://support.delicious.com/forum/comments.php?DiscussionID=2205
http://www.nabble.com/API-rate-limit--td15812267.html
http://therning.org/magnus/archives/237
来自 “ ITPUB博客 ” ,链接:http://blog.itpub.net/17131144/viewspace-614132/,如需转载,请注明出处,否则将追究法律责任。
转载于:http://blog.itpub.net/17131144/viewspace-614132/