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.

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

feat: subscription policies #15

Open
merklefruit opened this issue Oct 19, 2023 · 3 comments
Open

feat: subscription policies #15

merklefruit opened this issue Oct 19, 2023 · 3 comments
Labels
A-socket Area: Sockets C-feature Category: Feature

Comments

@merklefruit
Copy link
Contributor

As part of #13, we want to add the ability for subscribers to specify the "durability policy" that they want to use.
Here's how that would look like:

  • subscriber (ReqSocket or SubSocket) connects to a target, specifying the policy: if they would like to receive messages from the connection point onward, or if they want to also receive cached messages that were already broadcasted earlier than the connection time.
  • On the publisher's side there will always be a limit of how many messages to replay for the specific subscriber. Nonetheless, this will be useful for when clients are starting up to make sure they don't lose initial messages.
@merklefruit merklefruit added C-feature Category: Feature A-socket Area: Sockets labels Oct 19, 2023
@quangkeu95
Copy link
Contributor

quangkeu95 commented Nov 8, 2023

I can take on this.

@mempirate
Copy link
Contributor

@quangkeu95 this issue is blocked by #13, which we still need to figure out how to implement. Will ping you once we have a better idea of how to move forward!

@quangkeu95
Copy link
Contributor

sure, thanks for letting me know

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-socket Area: Sockets C-feature Category: Feature
Projects
None yet
Development

No branches or pull requests

3 participants