Built-in support for message compression #181
Conversation
Support for gzip, lz4 and snappy
snichme
requested review from
ThomasSarlin,
antondalgren,
baelter,
carlhoerberg and
dentarg
as code owners
|
I have had as a proud feature of this library that this is a 0 dependency library. Could we make the dependencies optional? |
| * @param properties - properties to be published | ||
| * @param [mandatory] - if the message should be returned if there's no queue to be delivered to | ||
| * @param [immediate] - if the message should be returned if it can't be delivered to a consumer immediately (not supported in RabbitMQ) | ||
| * @param options - publish options including compression settings |
There was a problem hiding this comment.
These methods should map closely to the protocol. Add compression to a high level client.
There was a problem hiding this comment.
I agree, we should build out BaseClient to have high level features like auto-reconnect, message coding, rpc client/server etc. Just like the ruby client. This is a WIP in that direction: #180
|
Nice! I agree with
IMHO we should build out BaseClient to have high level features like auto-reconnect, message coding, rpc client/server etc. Just like the ruby client. This is a WIP in that direction: #180 |
They are, since they are specified as |
@baelter sounds good, maybe combine this PR into #180 or at least base this branch on your |
Adds support for the producer to compress the payload by specifying compression algorithm, supported algos are gzip, lz4 and snappy. Looked at adding zstd but didn't find any packages with a synchronous API.
The consumer automatically picks up how the payload is compressed and decompresses it.
Each package is optional and it will be lazy loaded if needed.