@travisbell thanks travis. I have one more question. You have different base_url for images,for which someone again needs to fetch the configuration,which,sometimes,takes more time(4-5sec minimum) to be fetched. Is there any workaround that you can suggest me about the api,so that i can gather everything before my application starts ? Moreover the configuration is not cacheable . Thanks.
I have one more question. You have different base_url for images,for which someone again needs to fetch the configuration,which,sometimes,takes more time(4-5sec minimum) to be fetched.
Where are you located? Nothing should be taking 4-5 seconds, our response times are almost universally sub-100ms. Here's what the average looks like from our external monitoring.
Well i am from Hyderabad,india. I am using your apis for my learning purpose. And not cacheble means,when a ajax request is made to your api for configuration, the response data is not cached in browser and also i observed the response header,where there is a header which has value of maxage=0. I don't know whether its only happening in my case or others have seen it.
Ah, you're just talking about the Cache-Control header. Got it. Ya, that shouldn't be 0, and I can change that, but you can still cache the response within your app. I usually encourage users to check it once every week or so.
Thanks. Actually i tried with parameter 'cache:true', but its not caching the response. As you mentioned that you can change the cache-control header,so can you do that for me,plz ?
Yup, I've created a ticket for this here. I'm currently grooming some new engineers to work on TMDb with me and this will be one of the first tickets they work on, since it's a nice a simple task.
I will update this post when the changes have been pushed live.
Reply by Travis Bell
on December 11, 2019 at 10:15 AM
Not the API key, no, but you can send your account's access token as a
Authorization: Bearer
header. See the docs for more details.Reply by Sohan Kumar
on January 5, 2020 at 2:45 AM
@travisbell thanks travis. I have one more question. You have different base_url for images,for which someone again needs to fetch the configuration,which,sometimes,takes more time(4-5sec minimum) to be fetched. Is there any workaround that you can suggest me about the api,so that i can gather everything before my application starts ? Moreover the configuration is not cacheable . Thanks.
Reply by Travis Bell
on January 6, 2020 at 5:24 PM
Where are you located? Nothing should be taking 4-5 seconds, our response times are almost universally sub-100ms. Here's what the average looks like from our external monitoring.
What do you mean by it's not cacheable?
Reply by Sohan Kumar
on January 7, 2020 at 7:33 AM
Well i am from Hyderabad,india. I am using your apis for my learning purpose. And not cacheble means,when a ajax request is made to your api for configuration, the response data is not cached in browser and also i observed the response header,where there is a header which has value of maxage=0. I don't know whether its only happening in my case or others have seen it.
Reply by Travis Bell
on January 7, 2020 at 12:17 PM
Ah, you're just talking about the
Cache-Control
header. Got it. Ya, that shouldn't be 0, and I can change that, but you can still cache the response within your app. I usually encourage users to check it once every week or so.Reply by Sohan Kumar
on January 7, 2020 at 9:42 PM
Thanks. Actually i tried with parameter 'cache:true', but its not caching the response. As you mentioned that you can change the cache-control header,so can you do that for me,plz ?
Reply by Travis Bell
on January 12, 2020 at 11:44 AM
Yup, I've created a ticket for this here. I'm currently grooming some new engineers to work on TMDb with me and this will be one of the first tickets they work on, since it's a nice a simple task.
I will update this post when the changes have been pushed live.
Reply by Sohan Kumar
on January 12, 2020 at 12:43 PM
@travisbell thank you so much for your helps. 🙏