Geolocation is missing in the criteria for cache selection to serve content

[bsenel]

In a setup, I deployed five caches on the nodes located in distributed geolocations, for example, one in Europe, one in South America, one in North America, and so on. The problem is that the publisher selects the caches regardless of the client's location. It ignores the geographic location of caches that serve content at the selection. Why is this a problem?

For example, even if there is a cache in Paris, a client located in Paris also retrieves data chunks from a cache running in Rio. Additionally, the publisher includes the Rio cache even though it is the slowest option to serve content compared to the nodes located in the US. What I would expect from the publisher is to select caches that can serve content to the client faster.