The API is returning a next episode link that points to a episode that aired yesterday. For example:
http://api.tvmaze.com/singlesearch/shows?q=survivo...
Has "nextepisode":{"href":"http://api.tvmaze.com/episodes/167441"} and that episode aired YESTERDAY.
Same issue with numerous other shows, ie, survivor, the middle, top coppers
Thanks for your report, I see the caching should be a little less aggressive here. I'll have it fixed shortly!
Pardon my ignorance, but "caching" was something we heard a lot about over at TVRage, too.
What is it, and what are the upsides versus downsides?
I have an idea, but not everyone does. And I'm not sure I know the full story.
Gadfly wrote:
Pardon my ignorance, but "caching" was something we heard a lot about over at TVRage, too.
What is it, and what are the upsides versus downsides?
I have an idea, but not everyone does. And I'm not sure I know the full story.
I got no clue about such things :)
Gadfly wrote:
Pardon my ignorance, but "caching" was something we heard a lot about over at TVRage, too.
What is it, and what are the upsides versus downsides?
I have an idea, but not everyone does. And I'm not sure I know the full story.
There are various ways of caching data; TVmaze uses at least three of them. The very simplified gist of it is to temporarily store the result of an operation that's resource intensive to calculate; either for a predetermined time, or until the variables that influence the calculation are changed.
What happened here is that the stored result was sticking around a little too long, causing you to see outdated information.
