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

Avoid copying the files twice and still do everything asynchronously #4

Open
SteveGremory opened this issue Dec 2, 2022 · 1 comment
Labels
enhancement New feature or request

Comments

@SteveGremory
Copy link
Owner

No description provided.

@SteveGremory SteveGremory added the enhancement New feature or request label Dec 2, 2022
@SteveGremory
Copy link
Owner Author

An idea that I had when initially doing this was to take the worst-case file size after compression & encryption and basically use that as a writer limit for multiple writers which write to the same .zap archive at once then remove the empty spaces in the file if there are any.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant