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

Multiple subscriptions from the same consumer to the same endpoint? #388

Open
Tracked by #375
mlagally opened this issue Apr 17, 2023 · 1 comment
Open
Tracked by #375

Comments

@mlagally
Copy link
Contributor

mlagally commented Apr 17, 2023

Remove sentence: "To minimize network traffic, the same listerner MUST NOT perform multiple subscriptions to the same listener." (This sentence doesn't make sense. I think you meant to to say the same consumer must not perform multiple subscriptions to the same event, but I'm not sure that's a good idea. There may be use cases where the same Consumer needs to subscribe to the same event affordance but with different authentication credentials for example. It could instead perhaps be recommended to de-duplicate event notifications to the same listener URL where possible.)

@mlagally mlagally changed the title Remove sentence: "To minimize network traffic, the same listerner MUST NOT perform multiple subscriptions to the same listener." (This sentence doesn't make sense. I think you meant to to say the same consumer must not perform multiple subscriptions to the same event, but I'm not sure that's a good idea. There may be use cases where the same Consumer needs to subscribe to the same event affordance but with different authentication credentials for example. It could instead perhaps be recommended to de-duplicate event notifications to the same listener URL where possible.) Multiple subscriptions from the same consumer to the same endpoint? Apr 17, 2023
@mlagally
Copy link
Contributor Author

Remove sentence: "To minimize network traffic, the same listerner MUST NOT perform multiple subscriptions to the same listener." (This sentence doesn't make sense. I think you meant to to say the same consumer must not perform multiple subscriptions to the same event, but I'm not sure that's a good idea. There may be use cases where the same Consumer needs to subscribe to the same event affordance but with different authentication credentials for example. It could instead perhaps be recommended to de-duplicate event notifications to the same listener URL where possible.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants