Skip to content

Compress with a real DEFLATE encoder behind Deflater #63

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

Merged
Project516 merged 1 commit into from
Nov 6, 2026
Merged

Compress with a real DEFLATE encoder behind Deflater #63

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 4 additions & 3 deletions docs/support.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,9 +14,10 @@ java-web targets headless Java: console apps, libraries and javac.
shared with direct buffers and other native allocations. A mapping that does
not fit fails with `IOException: Map failed` and an `OutOfMemoryError` cause.
Read-write changes reach the file on force or unmap.
- `Deflater` writes valid DEFLATE streams using stored blocks. Compression
levels and strategies currently do not reduce output size; compressed bytes
and compression ratios differ from HotSpot's zlib output.
- `Deflater` is a DEFLATE compressor in TypeScript (`src/deflate.ts`) with
zlib's levels, strategies, flush modes, dictionaries and `setLevel` and
`setStrategy` changes. Compressed sizes are close to zlib's at each level, but
the bytes are not the same as HotSpot's zlib output.
- Child processes (`ProcessBuilder`, `Runtime.exec`, `ProcessHandle`) work
under Node and run the host's programs. Starting `java` starts another
java-web VM on the same image. A child cannot use a directory that exists only
Expand Down
Loading
Loading