This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
dido:public:ra:xapend:xapend.b_stds:tech:omg:dds_rpc [2021/08/09 15:06] murphy |
dido:public:ra:xapend:xapend.b_stds:tech:omg:dds_rpc [2021/08/17 13:20] (current) murphy [Scope] |
||
|---|---|---|---|
| Line 15: | Line 15: | ||
| ==== Scope ==== | ==== Scope ==== | ||
| - | ://The [[dido:public:ra:xapend:xapend.a_glossary:d:dds]] is widely used for [[dido:public:ra:xapend:xapend.a_glossary:d:dcps]] 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 [[dido:public:ra:xapend:xapend.a_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 portability and [[dido:public:ra:xapend:xapend.a_glossary:i:interoperability|interoperability]]. Such facility would allow commands to be naturally represented as remote method invocations. This presents a solution to this problem.// | + | ://The [[dido:public:ra:xapend:xapend.a_glossary:d:dds]] is widely used for [[dido:public:ra:xapend:xapend.a_glossary:d:dcps]] 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 [[dido:public:ra:xapend:xapend.a_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 [[dido:public:ra:xapend:xapend.a_glossary:p:portability|portability]] and [[dido:public:ra:xapend:xapend.a_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:xapend.b_stds:tech:ietf:1831]] framework using the basic building blocks of DDS, such as topics, types, DataReaders, and DataWriters to provide request/reply semantics. It defines distributed services, described using a service [[dido:public:ra:xapend:xapend.a_glossary:i:interface|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 [[dido:public:ra:xapend:xapend.a_glossary:c:corba|CORBA]].// | + | : //This specification defines a [[dido:public:ra:xapend:xapend.b_stds:tech:ietf:1831]] framework using the basic building blocks of DDS, such as topics, types, DataReaders, and DataWriters to provide request/reply [[dido:public:ra:xapend:xapend.a_glossary:s:semantics|semantics]]. It defines distributed services, described using a service [[dido:public:ra:xapend:xapend.a_glossary:i:interface|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 [[dido:public:ra:xapend:xapend.a_glossary:c:corba|CORBA]].// |