Tmdb API → Icebox

Hi Travis,

I was just wondering about this earlier, with my wrapper since 1.0 I always have had caching off by default, however if you'd follow the HTTP protocols and say amen to what TMDB gives back in the headers this just felt wrong. As such I have enabled caching by default from 2.0 onward, to both speed up the wrapper and relieve stress on the API side. Same goes for switching from http to https.

I was wondering if you have any intention or interest to make some sort of standard guide as how implementations should be done from your perspective? Whether it's caching or handling errors etc. I don't think this should be a must, not to discourage people to create wrappers, but act as a guideline as how it would be preferred to be implemented.

Wondering what your thoughts are!

Thanks,

Michael