View Single Post
Old 02-01-2011, 05:36 AM   #14
DoctorOhh
US Navy, Retired
DoctorOhh ought to be getting tired of karma fortunes by now.DoctorOhh ought to be getting tired of karma fortunes by now.DoctorOhh ought to be getting tired of karma fortunes by now.DoctorOhh ought to be getting tired of karma fortunes by now.DoctorOhh ought to be getting tired of karma fortunes by now.DoctorOhh ought to be getting tired of karma fortunes by now.DoctorOhh ought to be getting tired of karma fortunes by now.DoctorOhh ought to be getting tired of karma fortunes by now.DoctorOhh ought to be getting tired of karma fortunes by now.DoctorOhh ought to be getting tired of karma fortunes by now.DoctorOhh ought to be getting tired of karma fortunes by now.
 
DoctorOhh's Avatar
 
Posts: 9,897
Karma: 13806776
Join Date: Feb 2009
Location: North Carolina
Device: Icarus Illumina XL HD, Kindle PaperWhite SE 11th Gen
Quote:
Originally Posted by kovidgoyal View Post
Quote:
Originally Posted by dwanthny View Post
Their terms of service for standard no api key stuff was no more then 1 cover request per second. Is calibre exceeding that measure?
Easily. The very first LT plugin in calibre over a year ago was based on a webservice I wrote that forwarded requests to the LT server from my own server using an API key. That key was banned because it exceeded the limit, which is why I wrote the current plugin (after trying to contact LT and getting no response).
Does the current plugin forward the requests from your server or do the requests go directly from my computer to Library Thing?

If the requests go from my computer is it possible to have a throttle built into the plugin that limits cover requests to one per second or one every two seconds (maybe a user set number)? This might minimize Library Things interference with captcha verification you referred to in another thread.
DoctorOhh is offline   Reply With Quote