-
Notifications
You must be signed in to change notification settings - Fork 469
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
Download multiple children in a single request #9
Comments
Is anyone interested in this for the draft 1.0 spec? If so, can you please describe your use case? |
Requested by @e-andersson. |
Example: "tiles": {
"level1-id" : "0/0/0.b3dm"
},
// ...
"content": {
"tile": "level1-id",
"byteOffset": 0,
"byteLength": 1024
} |
This will be a great feature, but am pushing 1.0 to narrow scope. |
I know the link in the description alludes to this already, but given that HTTP/2 support is now standard in all browsers, is this still needed? Does it provide any benefit other than reducing the number of tile requests? |
Not sure when HTTP/2 support became available in each browser, but keep in mind that not all users are able to use the latest browser. |
@austinEng is evaluating HTTP/2 vs. combing vs. both. Results TBA soon. |
Awesome, looking forward to the results and methodology (since HTTP/2 server configuration probably comes into play as well) |
Would love to do this, but pushing post 1.0 for scope. |
This issue came up in discussion today. Some notes:
|
But HTTP/2 can already do this, right? |
See When using replacement refinement, can multiple children be combined into one request?.
The text was updated successfully, but these errors were encountered: