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.

Sign up for GitHub

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

Jump to bottom

Any i/o handle constructor taking a path_handle must take implementation from the path_handle #40

Open
ned14 opened this issue Oct 9, 2019 · 0 comments
Open

Any i/o handle constructor taking a path_handle must take implementation from the path_handle #40

ned14 opened this issue Oct 9, 2019 · 0 comments
Labels
enhancement

Comments

@ned14
Copy link
Owner

ned14 commented Oct 9, 2019

path_handle ought to be able to define the implementations of file_handle, directory_handle and so on. Then KV hardware can be supported by having path_handle return a file_handle which calls the SNIA KV API, or NTFS kv lookup can work if the path_handle refers to a NTFS volume, and so on.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@ned14