View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0004245 | 10000-014: PubSub | Api Change | public | 2018-04-17 11:36 | 2018-08-28 16:24 |
Reporter | Mariusz Postol | Assigned To | Matthias Damm | ||
Priority | normal | Severity | minor | Reproducibility | N/A |
Status | assigned | Resolution | open | ||
Platform | Any | OS | ANy | OS Version | Any |
Summary | 0004245: 6.2.1. PubSubState State Machine role is not clear | ||||
Description | The specification should promote the interoperability of the main actors taking part in the communication - exchanging messages. This state machine is not related to communication between Publisher and Subscribers, but it is related to local state management of something (PubSub Component ?), for example, PubSub Application instance as one whole, but it is not stated and this scenario is not very useful in practice. This state machine could be applied to Publisher/Subscriber, but the application instance could create many publishers and subscribers at the same time ?! We can ask what is the impact on the Publisher/Subscriber interoperability if someone will implement different state machine or there will be no state machine at all - always on. How to test interoperability? The state machine may be used by the configuration services Client/Server interoperability, so it should be moved to the configuration service model in section 9. | ||||
Tags | No tags attached. | ||||
Commit Version | |||||
Fix Due Date | |||||
Date Modified | Username | Field | Change |
---|---|---|---|
2018-04-17 11:36 | Mariusz Postol | New Issue | |
2018-04-24 14:18 | Jim Luth | Project | UA => 10000-014: PubSub |
2018-04-24 14:18 | Jim Luth | Category | Documentation Errata => Api Change |
2018-08-28 16:24 | Jim Luth | Assigned To | => Matthias Damm |
2018-08-28 16:24 | Jim Luth | Status | new => assigned |