2017-09-09, 07:28
(2017-09-05, 00:32)axlt2002 Wrote:(2017-09-05, 00:19)dziobak Wrote:(2017-09-04, 23:09)axlt2002 Wrote: So far I see the following two points (the first one is the most...serious):
- Starting from the TVDB ID, there will be one query to obtain the TheMovieDB_ID, another one to obtain the IMDB ID and a third one to query the IMDb site for updating the rates...it is also true that this will happen just at the first update (i.e. the IMDB ID should be saved for the next runs)
or you can cache this pairs TVDB ID->IMDB ID in local table -> write to file after, read from file before.
(2017-09-04, 23:09)axlt2002 Wrote:All the users will have to create their own API key...I don't want to provide support for that too!
You will make one API key only for application and this way is ok (for testing my little prog I used key from other app also)
I guess it would be preferrable to save the IMDB ID in the TV Show/Episode information of the Kodi library in the uniqueid field.
About the single API key...how it will be managed if used by differnet users? Let's say 100 users with a library of 100 Episodes (I guess it will be quite more...)...this is already bringing to 10000 requests to the site...do you know if there is a limit to the number if queries?
Easier said then done, but you can add a field where the user can populate their personal API Key
