W3C home > Mailing lists > Public > ietf-http-wg@w3.org > April to June 2017

draft-ietf-httpbis-header-compression-latest, "2.3.2 Dynamic Table"

From: <okis_chuang@trend.com.tw>
Date: Wed, 14 Jun 2017 02:56:05 +0000
Message-Id: <DB53C180-F8FA-48A1-9C89-29857DEB90B7@trend.com.tw>
To: "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>
<https://http2.github.io/http2-spec/compression.html#rfc.section.2.3.2 <https://http2.github.io/http2-spec/compression.html#rfc.section.2.3.2>>:

Hi,

Good day!

I have a question about the section "The encoder decides how to update the dynamic table and as such can control how much memory is used by the dynamic table. To limit the memory requirements of the decoder, the dynamic table size is strictly bounded (see Section 4.2 <https://http2.github.io/http2-spec/compression.html#maximum.table.size>).”

the decision about how to update the dynamic table is from “encoder” or “decoder”? I thought it is decoder.

Please correct me if it is not :)

Best Regards,

Okis Chuang
TREND MICRO EMAIL NOTICE
The information contained in this email and any attachments is confidential 
and may be subject to copyright or other intellectual property protection. 
If you are not the intended recipient, you are not authorized to use or 
disclose this information, and we request that you notify us by reply mail or
telephone and delete the original message from your mail system.

Received on Wednesday, 14 June 2017 07:37:31 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:15:03 UTC