Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Expose RequestScheduler in the public API #8384

Closed
lilleyse opened this issue Nov 12, 2019 · 2 comments · Fixed by #8549
Closed

Expose RequestScheduler in the public API #8384

lilleyse opened this issue Nov 12, 2019 · 2 comments · Fixed by #8549

Comments

@lilleyse
Copy link
Contributor

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.

In fact before RequestScheduler was introduced throttleRequestByServer.maximumRequestsPerServer was part of the public API.

Any reasons not to do this? It would be a quick PR.

@lilleyse lilleyse changed the title Expose RequestSchduler in the public API Expose RequestScheduler in the public API Nov 12, 2019
@wadeward
Copy link

wadeward commented Dec 9, 2019

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

@OmarShehata
Copy link
Contributor

@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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants