First of all, thanks for the fast reply. Second, thanks for all the effort on TADB
Now, back on topic. I fully understand your decision to limit the number of returned results in order to safeguard performance. I'm also happy to hear that the result limiting can be configured on a per-API key basis (I will soon apply for a key). Nevertheless, for supporting another possible use-case for TADB, I would have a suggestion for the next API update (fully backwards compatible).Use-case Description
What if users could use TADB for something other than scraping? With scraping you usually have an exact artist/album/track name, therefore as you said 5 results are more than enough. Alternatively, TADB could be used say for searching based on human (typed) input which is often inexact and often incomplete. In short, the additional scenario would be "using TADB for discovering new content for the user" rather than "using TADB for identifying the content the user already has".API Extension Proposal
What about adding an additional query parameter to your php pages to allow the user to configure the maximum number of returned results? Of course, the per-API key limiting will still be in effect.
For example, let's assume the API key "X", with a maximum number of returned results set by you at 100 results. The (fair) user, will then be allowed through the new parameter to restrict the number of returned results even further.Concrete example:http://www.theaudiodb.com/api/v1/json/X/search.php?s=ma%25
would return up to 100 results of artists whose names/alt names started with "ma".http://www.theaudiodb.com/api/v1/json/1/search.php?s=ma%25&l=20
would return up to 20 results of artists whose names/alt names started with "ma".
Of course, this would be just a first step towards supporting the presented use-case. One could think of Soundex fuzzy queries...
Please excuse the verbosity; old habits (die hard). Thanks for the support.