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

uSubscription spec/detail questions #239

Closed
AnotherDaniel opened this issue Sep 19, 2024 · 3 comments
Closed

uSubscription spec/detail questions #239

AnotherDaniel opened this issue Sep 19, 2024 · 3 comments
Assignees
Labels
question Further information is requested

Comments

@AnotherDaniel
Copy link
Contributor

During implementation of up-subscription-rust and the subsequent (and ongoing) specification rewrite (#238), so far these questions came up:

  • Is it expected that a uEntity can register more than one custom topic for receiving update notifications?
  • Is it supposed to be possible to register remote uuris as custom notification topics?
  • Should remote UUris be excluded from all listeners except subscribe and unsubscribe?
  • Do we need update/change notifications when remote SubscriptionResponses come in? Like, changing a topic status from SUBSCRIBE_PENDING to PENDING - which would then apply to every subscriber-topic combination at that point in time, with the corresponding number of Update messages…
  • Is SUBSCRIBE_PENDING a valid state to receive from a remote SubscriptionService as a response to a subscribe() call?
@stevenhartley
Copy link
Contributor

stevenhartley commented Sep 26, 2024

  • Is it expected that a uEntity can register more than one custom topic for receiving update notifications?

No you can not set the topic, notifications come on a fixed topic (the source URI)

  • Is it supposed to be possible to register remote uuris as custom notification topics?

Custom notification topics is not permitted

  • Should remote UUris be excluded from all listeners except subscribe and unsubscribe?

I think I need more info to understand what you mean here.

  • Do we need update/change notifications when remote SubscriptionResponses come in? Like, changing a topic status from SUBSCRIBE_PENDING to PENDING - which would then apply to every subscriber-topic combination at that point in time, with the corresponding number of Update messages…

Yes.

  • Is SUBSCRIBE_PENDING a valid state to receive from a remote SubscriptionService as a response to a subscribe() call?

No.

@stevenhartley stevenhartley added the question Further information is requested label Sep 26, 2024
@stevenhartley
Copy link
Contributor

Can we close this @AnotherDaniel ?

@stevenhartley
Copy link
Contributor

Closing issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants