Scenario
A client application that has a map. The map is an interactive control that, when moving / scaling, asks for the tile (as needed) from the tile server - GeoServer in this case, the tile server receives tile requests when the user moves around the interactive map. Suppose there is no limit to the number of requests a client can make.
Problem
When the user moves fast, requests to the tile server accumulate. The tile server is linked and cannot provide tiles in a timely manner.
In addition, the tile request queue responds in the request order. In this way, the user can travel from Florida to California and wait for the Florida tiles to be loaded before seeing any tiles in California.
Questions
How can we improve client perceived performance?
What are some client-side use strategies to prevent a large number of requests while panning fast? Fast scaling?
What are some strategies to use on the server side to determine if a request is needed or should it take a lower priority?
Possible Solution
- Tile Server , - . - , .
.