The GZIP spec includes support for one or more members (A gzip file consists of a series of "members" (compressed data sets).
but this spec currently states A gzip stream may only contain one "member"..
This is a request to be able to support decompressing multi-member gzip files to support use cases that depend on multi-member gzip (such as parsing ISO WARC).
Alternatively, if a way to get the unused data as in #39 would allow the developer to implement this manually, those ideal solution for my use case be native support for a multi-member DecompressionStream.
Could provide a proposed spec if there would be interest..
The GZIP spec includes support for one or more members
(A gzip file consists of a series of "members" (compressed data sets).but this spec currently states
A gzip stream may only contain one "member"..This is a request to be able to support decompressing multi-member gzip files to support use cases that depend on multi-member gzip (such as parsing ISO WARC).
Alternatively, if a way to get the unused data as in #39 would allow the developer to implement this manually, those ideal solution for my use case be native support for a multi-member DecompressionStream.
Could provide a proposed spec if there would be interest..