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

Tree Interface #170

Open
werkt opened this issue Sep 8, 2020 · 0 comments
Open

Tree Interface #170

werkt opened this issue Sep 8, 2020 · 0 comments

Comments

@werkt
Copy link
Collaborator

werkt commented Sep 8, 2020

A number of material differences exist for Trees throughout the API:

Directories are uploaded individually as blobs.
Trees are fetched in a list streaming fashion from getTree
OutputDirectories are represented as digests to whole-message Trees
The digests for OutputDirectories cannot use getTree to retrieve large directories pre-parsed.
In all of these circumstances, resolving directory references throughout the tree requires computed keying of a digest, with a specific hash function, and integrity throughout (related #159)
With likely others.

For v3, we should provide a transport and storage definition for trees that resolves this bespoke treatment of trees for input/output, and meets all criteria for an efficient and tractable representations

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

2 participants