Re: [quicwg/base-drafts] Make using static table and Huffman encoding in QPACK opt-in (#3622)

[Christian Huitema <[e-mail]>]

@vasilvv Picoquic pretty much fits in your target category, an endpoint that wants to implement a minimal version of HTTP/3. The strategy was indeed to set the SETTINGS_QPACK_MAX_TABLE_CAPACITY to zero, and also to never attempt Huffman encoding. It turns out that Huffman decoding is mandatory, but Huffman encoding is not.

To gauge the resulting capacity, you can look at the file "h3zero.c" and "h3zero.h" in the [picoquic distribution](https://github.com/private-octopus): 
```
ubuntu@ip-172-31-61-32:~/picoquic/picohttp$ wc h3zero.*
 1407  7726 61150 h3zero.c
  235   897  9024 h3zero.h
 1642  8623 70174 total
```
The code includes Qpack, Huffman, and the formatting and parsing of H3 messages. It uses static tables used for Qpack and Huffman decoding. The Huffman decoding accounts for 327 lines of tables and code in h3zero.c, 23% of the total.

Back to your point, yes there is some complexity, but no it is not overwhelming. The complexity is mostly in analyzing the specs and then coding them. I suppose I could extract "h3zero" in a separate project so minimal implementations could link with it without bothering with Picoquic proper. 

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/quicwg/base-drafts/issues/3622#issuecomment-623111609