hpack
hpack copied to clipboard
Listener interface causes lots of string creation & parsing overhead
Even though header names are required to be strings the interface emits them as byte[] which requires the recipient to decode and copy to create the equivalent string every time creating unnecessary garbage.
Additionally many common values have a parsed representation that is not a string:
- numeric type (:status)
- repeated value (content-encoding),
- more complex structure (P3P, User-Agent, ..)
- handler reference (:path)
Being able to store the representations that applications ultimately use with values cached in the hpack table will lower parsing costs.
@scottmitch @nmittler from Netty land
Related stuff https://github.com/netty/netty/issues/3597