This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
ddsf:public:guidebook:06_append:01_family_of_standards:03_ext:ddsrpc [2021/03/17 16:23] admin ↷ Links adapted because of a move operation |
ddsf:public:guidebook:06_append:01_family_of_standards:03_ext:ddsrpc [2021/07/14 15:55] (current) murphy ↷ Links adapted because of a move operation |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ===== OMG: RPC Over DDS (DDS-RPC) ===== | ===== OMG: RPC Over DDS (DDS-RPC) ===== | ||
| - | [[ddsf:private:guidebook:06_append:01_family_of_standards| return to the DDS Family of Standards ]] | + | [[ddsf:public:guidebook:06_append:01_family_of_standards:start| return to the DDS Family of Standards ]] |
| <table> | <table> | ||
| Line 15: | Line 15: | ||
| ==== Scope ==== | ==== Scope ==== | ||
| - | ://[[ddsf:private:guidebook:06_append:glossary:d:data_distribution_service_dds|The Data Distribution Service]] is widely used for [[ddsf:private:guidebook:06_append:glossary:d:data_centric]] publish/subscribe communication in real-time distributed systems. Large distributed systems often need more than one style of communication. For instance, data distribution works great for one-to-many dissemination of information. However, certain other styles of communication namely request/reply and remote method invocation are cumbersome to express using the basic building blocks of DDS. Using two or more [[ddsf:private:guidebook:06_append:glossary:m:midware|middleware]] frameworks is often not practical due to complexity, cost, and maintenance overhead reasons. As a consequence, developing a standard mechanism for request/reply style bidirectional communication on top of DDS is highly desirable for [[ddsf:private:guidebook:06_append:glossary:p:portability|portability]] and [[ddsf:private:guidebook:06_append:glossary:i:interoperability|interoperability]]. Such facility would allow commands to be naturally represented as remote method invocations. This presents a solution to this problem.// | + | ://[[ddsf:public:guidebook:06_append:glossary:d:data_distribution_service_dds|The Data Distribution Service]] is widely used for [[ddsf:public:guidebook:06_append:glossary:d:data_centric]] publish/subscribe communication in real-time distributed systems. Large distributed systems often need more than one style of communication. For instance, data distribution works great for one-to-many dissemination of information. However, certain other styles of communication namely request/reply and remote method invocation are cumbersome to express using the basic building blocks of DDS. Using two or more [[ddsf:public:guidebook:06_append:glossary:m:midware|middleware]] frameworks is often not practical due to complexity, cost, and maintenance overhead reasons. As a consequence, developing a standard mechanism for request/reply style bidirectional communication on top of DDS is highly desirable for [[ddsf:public:guidebook:06_append:glossary:p:portability|portability]] and [[ddsf:public:guidebook:06_append:glossary:i:interoperability|interoperability]]. Such facility would allow commands to be naturally represented as remote method invocations. This presents a solution to this problem.// |
| - | : //This specification defines a [[dido:public:ra:xapend.stds:tech:ietf:1831]] framework using the basic building blocks of DDS, such as topics, types, DataReaders, and DataWriters to provide request/reply [[ddsf:private:guidebook:06_append:glossary:s:semantics|semantics]]. It defines distributed services, described using a service interface, which serves as a shareable contract between service provider and a service consumer. It supports synchronous and asynchronous method invocation. Despite its similarity, it is not intended to be a replacement for [[ddsf:private:guidebook:06_append:glossary:c:corba|CORBA]].// | + | : //This specification defines a [[dido:public:ra:xapend.stds:tech:ietf:1831]] framework using the basic building blocks of DDS, such as topics, types, DataReaders, and DataWriters to provide request/reply [[ddsf:public:guidebook:06_append:glossary:s:semantics|semantics]]. It defines distributed services, described using a service interface, which serves as a shareable contract between service provider and a service consumer. It supports synchronous and asynchronous method invocation. Despite its similarity, it is not intended to be a replacement for [[ddsf:public:guidebook:06_append:glossary:c:corba|CORBA]].// |
| | | ||