Download multiple children in a single request about 3d-tiles HOT 11 OPEN

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

from 3d-tiles.

Requested by @e-andersson.

from 3d-tiles.

Example:

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

from 3d-tiles.

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

from 3d-tiles.

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?

from 3d-tiles.

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.

from 3d-tiles.

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

from 3d-tiles.

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

from 3d-tiles.

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

from 3d-tiles.

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

from 3d-tiles.

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?

from 3d-tiles.