Memory usage is still a problem but I think this feature can still be useful in some cases and it is standard so might as well implement it given it doesn't add too much to the API.

Thoughts on the API?@andersfylling@coadler@FZambia

It's not relevant to my use-cases as I use gzip, I think(?). But looks easy enough to use.

I would add a validation step on Treshold and Level field.

Sounds good.

Only issue I could forsee with this API is you can't control per message compression which I imagine is something people will want control over. But I'd have to break backwards compat and add a writer options structure to allow for that.

Or maybe just a way to disable compression for an individual message (that may already have some other form of compression, e.g. a JPEG image) but keep the level and threshold global to the connection.

🤔

Also, I noticed Facebook uses per message deflate for their chat, which has very small message sizes. Could either be a oversight or an optimization, not sure. 🤔