Vortex Cafe supports a subset of the DDS. This list shows all the Vortex Cafe supported features.
Vortex Café Supported Features
1. Supported DDS Profiles
Vortex Café supports the following DDS Profiles:
1.1.Minimum Profile
Supported with following limitations:
- Global:
- Listeners and statuses are not supported on DomainParticipants, Topics, Publishers and Subscribers
- Statuses are partially supported in DataReaders and DataWriters (see Statuses)
- QoS are not supported on DomainParticipants and Topics
- Participant :
- findTopic and lookupTopicDescription are not supported
- Publisher :
- waitForAcknowlegements is not supported
- DataWriter :
- waitForAcknowlegements is not supported
- getMatchedSubscriptions and getMatchedSubscriptionData are not supported
- getKeyValue is not supported
- cast is not supported
- Subscriber :
- getDataReaders and lookupDataReaders are not supported
- DataReader :
- waitForHistoricalData is not supported
- getMatchedPublications and getMatchedPublicationData are not supported
- readNextSample/takeNextSample are not supported
- lookupInstance is not supported
- getKeyValue is not supported
- cast is not supported
1.2 Ownership Profile
Fully supported.
1.3 Content-subscription Profile
This is partially supported.
Only a non-standard custom filter is available via the DataReader.Selector. More details can be found in the Vortex Cafe User guide which is part of the Vortex Cafe documentation. See User Guide section 3.3.1
1.4 Persistence Profile
This is not currently supported
1.5 Object Model Profile
This is not currently supported
2. Supported QoS Polices
The following table shows a list of the QoS Policies and which are supported in Vortex Cafe.
| QoS Policy | Supported |
|---|---|
| USER_DATA | No |
| TOPIC_DATA | No |
| GROUP_DATA | No |
| DURABILITY | Yes |
| DURABILITY_SERVICE | No |
| PRESENTATION | No |
| DEADLINE | Yes |
| LATENCY_BUDGET | Yes |
| OWNERSHIP | Yes |
| OWNERSHIP_STRENGTH | Yes |
| LIVELINESS | Partial |
| TIME_BASED_FILTER | Yes |
| PARTITION | Yes |
| RELIABILITY | Yes |
| TRANSPORT_PRIORITY | No |
| LIFESPAN | No |
| DESTINATION_ORDER | Yes |
| HISTORY | Yes |
| RESOURCE_LIMITS | Yes |
| ENTITY_FACTORY | Yes |
| WRITER_DATA_LIFECYCLE | Yes |
| READER_DATA_LIFECYCLE | Yes |
For the LIVELINESS Qos currently only AUTOMATIC is supported.
3. Supported DDS Statuses
The following table shows the list of supported DDS statuses (i.e. Listeners and WaitSet receive notification when these statuses change)
| Entity | Status Name | Supported |
|---|---|---|
| Topic | INCONSISTENT_TOPIC | No |
| Subscriber | DATA_ON_READERS | No |
| DataReader | SAMPLE_REJECTED | No |
| LIVELINESS_CHANGED | Yes | |
| REQUESTED_DEADLINE_MISSED | Yes | |
| REQUESTED_INCOMPATIBLE_QOS | No | |
| DATA_AVAILABLE | Yes | |
| SAMPLE_LOST | No | |
| DataWriter | LIVELINESS_LOST | No |
| OFFERED_DEADLINE_MISSED | Yes | |
| OFFERED_INCOMPATIBLE_QOS | Yes | |
| PUBLICATION_MATCHED | Yes |
