Skip to content

Conversation

@lukevalenta
Copy link
Contributor

@lukevalenta lukevalenta commented May 14, 2025

The Tile struct supports the tile format used by the Go checksum library (from which it was ported), but the tlog-tiles spec makes a few changes. Specifically, it fixes the height at 8 (so each tile has 256 elements), and uses the path element "entries" for data tiles.

With this change, we can remove custom path logic from the static_ct_api crate, although we still need to use the path element "data".

I don't love the "data_path_opt" field in tiles, but this seems like an OK way to support both "data" and "entries" as the data path element.

It will also allow us to support non-standard data tile paths like "extra_data", if we so choose.

The Tile struct supports the tile format used by the Go checksum library
(from which it was ported), but the tlog-tiles spec makes a few changes.
Specifically, it fixes the height at 8 (so each tile has 256 elements),
and uses the path element "entries" for data tiles.

With this change, we can remove custom path logic from the static_ct_api
crate, although we still need to use the path element "data".

I don't love the "data_path_opt" field in tiles, but this seems like an
OK way to support both "data" and "entries" as the data path element.
@lukevalenta lukevalenta requested a review from cjpatton May 14, 2025 15:34
@lukevalenta lukevalenta self-assigned this May 14, 2025
* Support non-data data path elements
* Support paths without height element
* Update tests
@lukevalenta lukevalenta merged commit ff857da into main May 16, 2025
1 check passed
@lukevalenta lukevalenta deleted the lvalenta/tlog-tiles branch May 16, 2025 16:25
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

Successfully merging this pull request may close these issues.

2 participants