Tasks #53
Think about scope subscriptions for spread
| Status: | Rejected | Start date: | 08/19/2010 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | - | % Done: | 0% | |
| Category: | - | |||
| Target version: | - |
Description
If one subscription is used multiple times in the subscribe call, how to handle joining and leaving spread groups? E.g. two subscribe calls with the same subscription object and only one unsubscribe should probably completely unsubscribe the subscriber. But how can the SpreadPort know this? It can only count the number of Subscriptions for one URI received from the ScopeFilter. Who ensures that the port only receives unique subscriptions and unsubscribe calls?
History
#1 Updated by S. Wrede over 13 years ago
Probably, we could add a uuid also to the subscription objects that can be evaluated by the ports.
#2 Updated by S. Wrede over 13 years ago
- Subject changed from Think about scop subscriptions for spread to Think about scope subscriptions for spread
#3 Updated by J. Wienke almost 13 years ago
- Status changed from New to Rejected
This has completely changed with the current model.