Earlier quoted context omitted.
One of the main differences is this one uses lookup tables for faster decoding of Huffman compressed data as opposed to using a tree (which is what the stdlib one uses). It also offers some additional encoding options for users that want more control of header field indexing.
Yes, let's get your version into Go if it's better. (I wrote Go's quickly. I've never profiled it, delaying that until Go 1.7, which opened for development yesterday)
Show HN: HTTP/2 HPACK Compression Go Library
11–15 of 15 posts
Re: Show HN: HTTP/2 HPACK Compression Go Library
#12Earlier quoted context omitted.
Yes, let's get your version into Go if it's better. (I wrote Go's quickly. I've never profiled it, delaying that until Go 1.7, which opened for development yesterday)
If I'd like to get some of the enhancements in there, is this the route to go? https://golang.org/doc/contribute.html
I'd start with filing a bug against Go to track the overall process.
Re: Show HN: HTTP/2 HPACK Compression Go Library
#13Re: Show HN: HTTP/2 HPACK Compression Go Library
#14Earlier quoted context omitted.
If I'd like to get some of the enhancements in there, is this the route to go? https://golang.org/doc/contribute.html
Yup! That documentation is too daunting IMO but it's complete and not many steps, despite all the words. Especially if you're a Go programmer already. (just go get the code review tool) I'd start with filing a bug against Go to track the overall process.
Fantastic.