linking dds libraries

4 posts / 0 new
Last post
Offline
Last seen: 6 years 11 months ago
Joined: 07/03/2013
Posts: 3
linking dds libraries

Hello,

I have some applications which have to communicate, and which share the same OS. So they are in the same node.

Do i have to link DDS libraity and services within each application or do I have to run the service only on the OS  by declaring

each application as subscriber, publisher or both

RGDS

Gerardo Pardo's picture
Offline
Last seen: 1 month 1 week ago
Joined: 06/02/2010
Posts: 591

Hello,

You have to link the RTI Connext DDS libraries into each application. There is no separate service needed to run RTI DDS applications. All you need are your own applications linked with the DDS libraries. Any application can be a publisher, a subscriber or both. This is determined by the calls the application itself makes, that is, whether it creates DDS DataWriters, DataReaders, or both.

Regards,

Gerardo

 

Offline
Last seen: 6 years 11 months ago
Joined: 07/03/2013
Posts: 3

Ok,

But what about the middleware Connext!? it will run on each application through the liraries or it will run on the OS shared by all applications.?

rip
rip's picture
Offline
Last seen: 5 days 21 hours ago
Joined: 04/06/2012
Posts: 321

"Connext" is the family name for four products, Connext DDS, Connext Messaging, Connext Integrator and Connext Micro.  DDS and Messaging are library-based.  In order for your application(s) to take part on the DDS bus, they each have to link against the libraries, in order to pick up the capabilities supplied.  There is no 'server' or broker involved, every application will be a full peer on the bus.

Integrator supplies some additional capabilities, which are simply applications that extend or enable additional, optional, capabilities.  These are things like the Routing Service, Record/Replay, Database Integration Service, etc.  These are also not "servers", they are simply DDS peer applications on the bus.

Nothing is "shared" as that implies 'server' and 'single-point-of-failure'.  Each application will have its own Domain Participant(s), and each DP will have its own memory/threads/resources.  There is a shared memory transport so that DPs on the same node can use that to communicate via DDS, but other than the shared memory segment (which can be configured out), there are no shared resources.  Each application is self-contained. 

Rip