Summary
The Publish and Subscribe API enables a client to access context sensitive information.
Supported Functionality
Requirement |
Description |
Data |
- Data shall be represented by a key and a value.
- The value shall be a variant type.
|
Hierarchical Data |
- Data shall be organized within a hierarchy. Note that this does not imply that the underlying data structure is hierarchical.
- It shall be possible for the data to represent and ontology.
- Structure supports introspection at runtime.
|
Publish |
- It shall be possible clients to publish data.
- It shall be possible for clients to publish data for which an existing key does not already exist.
- It will not be necessary for clients accessing the published data to be aware of which client published the data.
|
Data Deletion |
- It shall be possible for a client to delete data removing both the value and the key.
|
Data Discovery |
- The Publish and Subscribe system shall enable the discovery of all published (and non-yet published) data .
|
Subscription |
- It shall be possible for clients to access the data at the client's own discretion by making a query or listening on an event channel to get information.
|
Clients Publish and Subscribe |
- It shall be possible for applications to act as both subscriber and publisher.
|