See: Description
Interface | Description |
---|---|
CommunicationListener<ENTITY_DATA extends DiscoveredData> |
CommunicationListener is used by applications that need to know
of different CommunicationStatuses, as specified n DDS specification.
|
ContentFilter<T> |
ContentFilter.
|
EntityListener |
EntityListener.
|
HistoryCache<T> |
HistoryCache represents a uDDS history cache.
|
SampleListener<T> |
A listener for samples.
|
Class | Description |
---|---|
DataReader<T> |
This class represents a strongly typed DataReader in spirit of DDS specification.
|
DataWriter<T> |
This class represents a strongly typed DataWriter in spirit of DDS specification.
|
Entity<T,ENTITY_DATA extends DiscoveredData> |
Entity is a base class for DataReader and DataWriter.
|
EntityFactory |
EntityFactory is used to create instances of uDDS entities.
|
Instance<T> |
Instance represents Samples with same distinct ID.
|
Participant |
Participant acts as a communication endpoint of different data.
|
Annotation Type | Description |
---|---|
Key |
This annotation provides means to tag fields as being part of a RTPS(DDS)
key.
|
Type |
This annotation is used to set the topic name and type name of the DDS object/topic.
|
uDDS aims to be a simplistic version of DDS specification by OMG. Idea is to simplify writing code to DDS domain, while keeping programming interface as simple as possible. While using jRTPS, uDDS can talk to any vendors DDS implementation, as long as RTPS is used as a communication protocol. There might(and probably will) be some limitations on what parts of the DDS specification ends up being supported by uDDS.
Copyright © 2016. All rights reserved.