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
All highscores calls result in two tibia.com requests, one for check world, other to get highscore.
We can reduce execution time in 50% caching worlds list from worlds and when need to check if a world exists, check in this array. Considering that it is not normal to have new worlds, we can cache for 24 hours or more.
The text was updated successfully, but these errors were encountered:
I see no point in caching the results. This is how a crawler works, always get the bleeding edge data even if it doesn't change for a long period. But I think there is a problem in making those double requests, we can skip the first (to check if the world exists) and just try to get the world highscores, and let it scream if the world doesn't exists normally. What do you think?
PS: Whoever made this highscore function got it completely out of code style standards, please fix it.
All
highscores
calls result in two tibia.com requests, one for check world, other to get highscore.We can reduce execution time in 50% caching worlds list from
worlds
and when need to check if a world exists, check in this array. Considering that it is not normal to have new worlds, we can cache for 24 hours or more.The text was updated successfully, but these errors were encountered: