Move (de)compression to Web Workers #72
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Alternative to #71 - does almost the same in a slightly different way. This PR once again adds a separate class for built-in compression implementation (gzipped MessagePack) and makes use of it in the Storage implementation. Unlike upstream, this compression is applied on a lower level, so all files are compressed instead of just RWProxy and other explicit usages. There needs to be a way to bypass this, and that's exactly why the Storage constructor optionally accepts a different storage interface. This may be useful for mods once they get own data directories.
Unlike #71 this implementation creates a new worker for each operation, which may help with intensive compression operations; workers are terminated after use. Error handling for workers may be simplified once
Error.isErrorbecomes available in Electron.