How are we meant to cache the request? Theres no ETag or anything. As in, how are we meant to check if for example: api/3/{movie/tv}/{tmdbid} is updated? I can cache using localStorage, but how am I meant to know if I should use the cached version, or re-grab. Is there any /sync/last_activities like Trakt?
Kan du ikke finde en film eller TV-serie? Log in og opret den.
Want to rate or add this item to a list?
Ikke medlem?
Svar af jamesb16
d. 22 februar 2018 kl. 6:46 PM
pragma account cracker, movie watcher :))
Svar af Travis Bell
d. 23 februar 2018 kl. 1:55 PM
Hey @PRAGMA,
Etags have been restored. I thought it was odd to hear it wasn't present as I know I looked into this years ago and indeed, it was a bug introduced a few months ago.
Svar af rlaphoenix
d. 23 februar 2018 kl. 5:46 PM
ETag isnt on /discover is this expected?
Svar af Travis Bell
d. 23 februar 2018 kl. 5:53 PM
Yes, for now. Etags were easy to restore on our Ruby stack. People, discover, search, lists and v4, are all on our Lua stack. That's an entirely different thing.
Svar af rlaphoenix
d. 23 februar 2018 kl. 5:55 PM
Alright, and just to confirm, I should store the Etag on first request, and then when re-doing the request, do If-None-Match: and that will send the request but wont count towards rate-limit right?
Svar af Travis Bell
d. 23 februar 2018 kl. 5:57 PM
That's the correct strategy yes, but I don't believe our rate limiting is sophisticated enough to not make that request count. I believe it still counts.
Svar af rlaphoenix
d. 23 februar 2018 kl. 6:48 PM
Then wouldnt using Etag on /movie/{id}/ essentially useless?
Svar af Travis Bell
d. 23 februar 2018 kl. 6:55 PM
Not really, it saves you from downloading the response. In any case, none of this has really ever been supported (etags didn't even work for ~3 months)
One day perhaps things will get an update to be smarter about this, but in order to make the rate limiting aware of
If-None-Match
is actually a huge re-factor of the way our infrastructure works today. Rate limiting stands in front of our app infrastructure as a standalone service so it has no idea what happens once you've been allowed through. A 200, 404 or HEAD, are all the same to it.Svar af rlaphoenix
d. 23 februar 2018 kl. 7:19 PM
But doing an Etag still responds a JSON result though?
Svar af Travis Bell
d. 25 februar 2018 kl. 11:45 AM
Yes, if the response has changed. It's a conditional call, look at the following as examples:
Repsonds with the body as a regular
200
response. Now if we make another request with theETag
we got back in the first request, you'll see it responds with no body, as a304
response.Now, let's say the
ETag
changes (I'll fake this by changing the ETag I query):You get another
200
response with the body and a newETag
.