You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Some times the server returns incorrect ratings (because of title collisions) and even if the correct rating is available at a later point, the app never requests the rating again. So the app shows incorrect rating to the user.
Describe the solution you'd like
We already have a timestamp column in the database table MOVIE_RATINGS. The app is not using at this time, but we can start adding the timestamp when the rating is fetched. We can have a threshold of 2 weeks and the if the app requests the rating after 2 weeks, it would check the timestamp and get the rating online.
Additional context
This would potentially increase in the app sending more requests to the server, but we can consider it as marginal since the threshold is 2 weeks. This would also help getting better trending movies.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Some times the server returns incorrect ratings (because of title collisions) and even if the correct rating is available at a later point, the app never requests the rating again. So the app shows incorrect rating to the user.
Describe the solution you'd like
We already have a timestamp column in the database table
MOVIE_RATINGS
. The app is not using at this time, but we can start adding the timestamp when the rating is fetched. We can have a threshold of 2 weeks and the if the app requests the rating after 2 weeks, it would check the timestamp and get the rating online.Additional context
This would potentially increase in the app sending more requests to the server, but we can consider it as marginal since the threshold is 2 weeks. This would also help getting better trending movies.
The text was updated successfully, but these errors were encountered: