You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
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?
During implementation of up-subscription-rust and the subsequent (and ongoing) specification rewrite (#238), so far these questions came up:
subscribe
andunsubscribe
?The text was updated successfully, but these errors were encountered: