![]() Non-conforming blocks must not be created by CompressionStream, and are errors for DecompressionStream. Implementations must be "compliant" as described in section 1.4. It is an error if there is additional input data after the ADLER32 checksum. It is an error for DecompressionStream if the ADLER32 checksum is not correct. The FLEVEL flag is ignored by DecompressionStream. The FDICT flag is not supported by these APIs, and will error the stream if set. The only valid value of the CM (Compression method) part of the CMF field is 8. įield values described as invalid in must not be created by CompressionStream, and are errors for DecompressionStream.Implementations must be "compliant" as described in section 2.3. Note: This format is referred to as "deflate" for consistency with HTTP Content-Encodings. A compression context is initially in a start state such that it anticipates the first byte of input. From the point of view of this specification, it is an opaque object. The contents of a compression context depend on the format, algorithm and implementation in use. Ī compression context is the internal state maintained by a compression or decompression algorithm. The terms ReadableStream and WritableStream are defined in. They accept any BufferSource type as input.Ī stream represents an ordered sequence of chunks. In the case of CompressionStream and DecompressionStream, the output chunk type is Uint8Array. Specification uses that specification and terminology. Specification MUST implement them in a manner consistent with the ECMAScriptīindings defined in the Web IDL specification, as this Implementations that use ECMAScript to implement the APIs defined in this Particular, the algorithms defined in this specification are intended to beĮasy to follow, and not intended to be performant.) Implemented in any manner, so long as the end result is equivalent. The user agent that implements the interfaces that it contains.Ĭonformance requirements phrased as algorithms or specific steps may be This specification defines conformance criteria that apply to a single product: The key words MUST and SHOULD are to be interpreted as described in. ConformanceĪs well as sections marked as non-normative, all authoring guidelines,ĭiagrams, examples, and notes in this specification are non-normative.Įverything else in this specification is normative. They support "deflate", "deflate-raw" and "gzip" as compression algorithms. The APIs specified in this specification are used to compress and decompress streams of data. 8.2 Deflate-compress an ArrayBuffer to a Uint8Array.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |