- Thread starter
- Moderator
- #231
Re: SubtitleDownloader 2.6
You are talking about "sites" but is your experience really based only on Bierdopje?
In that case I can say that the API for Bierdopje is not very good in performance point of view if compared to other APIs. At this point I don't remember all the details but the Bierdopje API requires doing "extra" requests for simple searches SubtitleDownloader does. Also, the implementation for Bierdopje was not originally made by me but I did some optimizations for it. For these optimizations I had to compile my own version of Bierdopje C# API DLL since there were protected methods in original implementation that I could not use directly for optimization purposes.
In general I think the Bierdopje API is too complex for SubtitleDownloader. Caching is not a solution but only a hack to work around the poor API. SubtitleDownloader is intented to be a light-weight library and a database is certainly not going to be part of it. Also if you check the version history of my DLL I have always made optimizations when possible since I don't have any reason to make SubtitleDownloader perform poorly by making extra requests.
Of course you are always welcome to post your optimized implementation for any site.
Hi Seco,
It has come to my attention that this plugin is not really "API Friendly" for the sites providing those.
It executes calls, that can be cached very easy since they provide data that never change. By caching it, you would improve the speed of the addon ánd decrease the strain you put on the subtitle site's so it is a win-win situation.
For example, you are using Bierdopje's "FindShowByName" call to obtain the show id.
This ID is "fixed" and never changes, so if you would cache this (e.g. in an sqlite database?) it would eliminate a lot of API calls and improving the general performance.
I think the subtitle sites can appreciate this, just like the endusers.
You are talking about "sites" but is your experience really based only on Bierdopje?
In that case I can say that the API for Bierdopje is not very good in performance point of view if compared to other APIs. At this point I don't remember all the details but the Bierdopje API requires doing "extra" requests for simple searches SubtitleDownloader does. Also, the implementation for Bierdopje was not originally made by me but I did some optimizations for it. For these optimizations I had to compile my own version of Bierdopje C# API DLL since there were protected methods in original implementation that I could not use directly for optimization purposes.
In general I think the Bierdopje API is too complex for SubtitleDownloader. Caching is not a solution but only a hack to work around the poor API. SubtitleDownloader is intented to be a light-weight library and a database is certainly not going to be part of it. Also if you check the version history of my DLL I have always made optimizations when possible since I don't have any reason to make SubtitleDownloader perform poorly by making extra requests.
Of course you are always welcome to post your optimized implementation for any site.