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

Download multiple children in a single request #9

Open
pjcozzi opened this issue Jul 31, 2015 · 11 comments
Open

Download multiple children in a single request #9

pjcozzi opened this issue Jul 31, 2015 · 11 comments

Comments

@pjcozzi
Copy link
Contributor

pjcozzi commented Jul 31, 2015

See When using replacement refinement, can multiple children be combined into one request?.

We may design 3D Tiles to support downloading all children in a single request by allowing tiles.json to point to a subset of a file for a tile's content similiar to glTF buffer and bufferView.

@pjcozzi
Copy link
Contributor Author

pjcozzi commented Apr 13, 2016

Is anyone interested in this for the draft 1.0 spec? If so, can you please describe your use case?

@pjcozzi
Copy link
Contributor Author

pjcozzi commented Jun 15, 2016

Requested by @e-andersson.

@pjcozzi
Copy link
Contributor Author

pjcozzi commented Jul 23, 2016

Example:

"tiles": {
    "level1-id" : "0/0/0.b3dm"
},
// ...
"content": {
  "tile": "level1-id",
  "byteOffset": 0,
  "byteLength": 1024
}

@pjcozzi pjcozzi removed the draft 1.0 label Jan 11, 2017
@pjcozzi
Copy link
Contributor Author

pjcozzi commented Jan 11, 2017

This will be a great feature, but am pushing 1.0 to narrow scope.

@mramato
Copy link

mramato commented Apr 6, 2017

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?

@GatorScott
Copy link

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.

@pjcozzi
Copy link
Contributor Author

pjcozzi commented Apr 12, 2017

@austinEng is evaluating HTTP/2 vs. combing vs. both. Results TBA soon.

@mramato
Copy link

mramato commented Apr 13, 2017

Awesome, looking forward to the results and methodology (since HTTP/2 server configuration probably comes into play as well)

@pjcozzi
Copy link
Contributor Author

pjcozzi commented Apr 6, 2018

Would love to do this, but pushing post 1.0 for scope.

@ptrgags
Copy link
Contributor

ptrgags commented Sep 23, 2021

This issue came up in discussion today. Some notes:

  • gRPC (or other similar library) might be useful to make a server/client architecture that can bundle tiles together in a single request
  • If we do add something like this to the spec, it would be an optional architecture best used with large tilesets. Serving tilesets as static files is still a valuable feature
  • this might pair well with 3DTILES_implicit_tiling in the future, as the availability buffers will be helpful in locating tiles to request on the server.

CC @lilleyse @sanjeetsuhag

@kring
Copy link
Member

kring commented Sep 24, 2021

gRPC (or other similar library) might be useful to make a server/client architecture that can bundle tiles together in a single request

But HTTP/2 can already do this, right?

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

No branches or pull requests

6 participants