Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

SubSocket: specify decompressor on a connection level #41

Closed
mempirate opened this issue Dec 8, 2023 · 1 comment · Fixed by #45
Closed

SubSocket: specify decompressor on a connection level #41

mempirate opened this issue Dec 8, 2023 · 1 comment · Fixed by #45
Assignees
@merklefruit
Labels
A-compression Area: Compression C-feature Category: Feature M-good-first-issue Meta: Good first issue

Comments

@mempirate
Copy link
Contributor

Context

Currently we can only specify a single decompressor that gets used across all publisher connections. It is likely however that a subscriber will subscribe to multiple publishers, that all use a different compression format. We should therefore be able to specify a decompressor per connection (i.e. as a connect option).
@mempirate mempirate added A-compression Area: Compression C-feature Category: Feature M-good-first-issue Meta: Good first issue labels Dec 8, 2023
@merklefruit
Copy link
Contributor

An alternative to this feature is proposed in #43: Message-level compression

@merklefruit merklefruit mentioned this issue Dec 18, 2023
Merged
@merklefruit merklefruit self-assigned this Dec 19, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@merklefruit merklefruit

Labels
A-compression Area: Compression C-feature Category: Feature M-good-first-issue Meta: Good first issue
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

feat: Pub/Sub auto-decompression chainbound/msg-rs
2 participants
@mempirate @merklefruit