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

API: Avoid reading directly from file system #1

Open
forderud opened this issue Jan 6, 2016 · 0 comments
Open

API: Avoid reading directly from file system #1

forderud opened this issue Jan 6, 2016 · 0 comments

Comments

@forderud
Copy link
Member

forderud commented Jan 6, 2016

Investigate if it may make sense to replace direct file access with stream-based IO based on IStream, so that the loaders does not need to touch the filesystem directly.

REF: https://msdn.microsoft.com/en-us/library/windows/desktop/aa380034.aspx

Advantages:

  • Enables sandboxing of loaders (can run in separate process with reduced privileges)
  • File/network agnostic.
  • Avoid problems with file locking.

Limitations:

  • Added complexity due to need for implementing IStream.
  • More complex loader and/or integration code.
jogerh pushed a commit that referenced this issue Oct 19, 2016
Fix Orientation and other issues
forderud pushed a commit that referenced this issue Aug 14, 2017
Fix Orientation and other issues
forderud pushed a commit that referenced this issue Feb 23, 2018
Get three planes instead of the whole volume block
forderud pushed a commit that referenced this issue Jul 27, 2018
@forderud forderud added this to the 2.x milestone Aug 28, 2018
@forderud forderud changed the title Stream-based IO API: Avoid reading files directly from file system Aug 28, 2018
@forderud forderud changed the title API: Avoid reading files directly from file system API: Avoid reading directly from file system Aug 28, 2018
@forderud forderud modified the milestones: 2.x, 3.x Aug 28, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant