Config about tmdblib HOT 1 CLOSED

Ok, I know you'll just say it should be in the docs. But here's the reason.

The Movie DB is built for a variable set of image sizes. They can add or remove sizes as they see fit. So to avoid updating the library every time they do so, I made it so that the library needs to download the config first.

http://docs.themoviedb.apiary.io/#configuration

But because this is a network activity, it's bad behaviour to do this in the constructor. Imagine if you had no network (or other errors), then you'd need to code like this:

Client client;
try {
client = new Client(..);
}
catch {
// Bad network ...
}

I persoanlly prefer not doing work in constructors, and leave it to the individual methods. Then to combat requesting the config at every instantiation, I allowed importing the config from elsewhere (say, a cached save file).

Also, imagine what would happen if you had threads (say, a server processing clients), that all needed to do stuff with TMDb. I haven't designed or tested the library for threadsafe-ness, so you may need to instantiate a new client pr. server connection. Should those also request configs? :P

But that should go in the docs. True.
I'll refer to issue #21 on this.

from tmdblib.