zlib-ng for websocket permessage-deflate?

[bgemmill]

In a prior issue, I was asking about using a system zlib, or boost::iostreams when the motivating example was CVE tracking.

I'm working on a piece of code now that consumes a really large amount of compressed websocket messages, and spends a large amount of run time decompressing them in beast's zlib implementation according to perf.

This piece of code is performance sensitive, and I'd like to try using zlib-ng or Cloudflare's fork to see about speeding that up.

Is there any way to make a websocket connect with permessage deflate and then let the user supply the implementation?

[vinniefalco]

That depends, is the zlib-ng API identical to regular zlib?

[bgemmill]

zlib-ng's API is identical (or they take bug reports) if compiled in zlib-compat mode, which provides a zlib.h.

[bgemmill]

@vinniefalco is there a good way to approach this as a user of beast, or does this require beast to be changed to use zlib.h?

If the second, happy to have a go at a PR if you can point me in the right direction.

[vinniefalco]

Yes, in theory Beast could be refactored to acquire the compressor from some singleton that can be reconfigured, if the APIs are the same.