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
We should consider exposing parts of RequestScheduler in the public API, especially concurrency settings like maximumRequests, maximumRequestsPerServer, requestsByServer, and throttleRequests. This would give developers more control over tile request concurrency.
Hi guys, just following up on this request . Is it possible that you can provide us an angular-cesium example of how to use the TileProviderError , such as a small snippet of code just to understand how best to capture the errorEvent..thanks
@wadeward I think your question is not related to this issue. Please open a thread in the Cesium forum with some more information on what you're trying to do.
We should consider exposing parts of
RequestScheduler
in the public API, especially concurrency settings likemaximumRequests
,maximumRequestsPerServer
,requestsByServer
, andthrottleRequests
. This would give developers more control over tile request concurrency.In fact before
RequestScheduler
was introducedthrottleRequestByServer.maximumRequestsPerServer
was part of the public API.Any reasons not to do this? It would be a quick PR.
The text was updated successfully, but these errors were encountered: