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

Clarify use cases for multitiles. How to limit request volume. #13

Open
joanma747 opened this issue Mar 4, 2020 · 2 comments
Open

Clarify use cases for multitiles. How to limit request volume. #13

joanma747 opened this issue Mar 4, 2020 · 2 comments

Comments

@joanma747
Copy link
Contributor

joanma747 commented Mar 4, 2020

These comments came out form the WMS.SWG Toulouse 2019 meeting:

  • Leave multitiles out of the core.
  • Better specify the use cases for multitiles
  • Need to limit the “volume” of the requests
@joanma747
Copy link
Contributor Author

Default request is too demanding. Takes everything!!. Need for assincronous

@aaime
Copy link

aaime commented Mar 30, 2020

Asynchronous is most welcomed. One could also leave synchronous for formats that can be just streamed out, one tile at a time (e.g. a zip file full of tiles, a multipart). But for common formats, say geopackage, mbtiles, then yes, asynch is a must.

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

No branches or pull requests

3 participants