Discussion:
[OSPL-Dev] bi directional communication between publisher and subscriber
Ravi Chandran
2011-07-12 04:51:56 UTC
Permalink
hi all,
I wanted to know whether bi-directional communication is possible in
opensplice DDS between a publisher and subscriber or not.. Or do we have to
integrate both publisher and subscriber code at both the ends
to fulfill it?
--
Thanks & Regards
Ravi
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://dev.opensplice.org/pipermail/developer/attachments/20110712/8f5dd696/attachment.htm>
Hans van't Hag
2011-07-12 07:51:20 UTC
Permalink
Hi Ravi,



The OMG-DDS specification mandates the flow of information from a
Publisher/Writer to a Subscriber/Reader. So any DDS-implementation
(including OpenSplice) requires both a publisher/writer as well as
subscriber/reader at 2 ends if you want bi-directional flows.



Regards,

Hans





* *

*Hans van 't Hag*

OpenSplice DDS Product Manager

PrismTech Netherlands

Email: hans.vanthag at prismtech.com

Tel: +31742472572

Fax: +31742472571

Gsm: +31624654078



PrismTech is a global leader in standards-based, performance-critical
middleware. Our products enable our OEM, Systems Integrator, and End User
customers to build and optimize high-performance systems primarily for
Mil/Aero, Communications, Industrial, and Financial Markets.
------------------------------

*From:* developer-bounces at opensplice.org [mailto:
developer-bounces at opensplice.org] *On Behalf Of *Ravi Chandran
*Sent:* Tuesday, July 12, 2011 6:52 AM
*To:* OpenSplice DDS Developer Mailing List
*Subject:* [OSPL-Dev] bi directional communication between publisher
andsubscriber



hi all,

I wanted to know whether bi-directional communication is possible in
opensplice DDS between a publisher and subscriber or not.. Or do we have to
integrate both publisher and subscriber code at both the ends
to fulfill it?
--
Thanks & Regards

Ravi
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://dev.opensplice.org/pipermail/developer/attachments/20110712/7bc3f4d9/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/jpeg
Size: 3349 bytes
Desc: not available
URL: <Loading Image...>
Ravi Chandran
2011-07-12 09:29:39 UTC
Permalink
Okay, Thanks. I will implement it at both ends then..

On Tue, Jul 12, 2011 at 1:21 PM, Hans van't Hag
Post by Hans van't Hag
Hi Ravi,
The OMG-DDS specification mandates the flow of information from a
Publisher/Writer to a Subscriber/Reader. So any DDS-implementation
(including OpenSplice) requires both a publisher/writer as well as
subscriber/reader at 2 ends if you want bi-directional flows.
Regards,
Hans
* *
*Hans van 't Hag*
OpenSplice DDS Product Manager
PrismTech Netherlands
Email: hans.vanthag at prismtech.com
Tel: +31742472572
Fax: +31742472571
Gsm: +31624654078
PrismTech is a global leader in standards-based, performance-critical
middleware. Our products enable our OEM, Systems Integrator, and End User
customers to build and optimize high-performance systems primarily for
Mil/Aero, Communications, Industrial, and Financial Markets.
------------------------------
developer-bounces at opensplice.org] *On Behalf Of *Ravi Chandran
*Sent:* Tuesday, July 12, 2011 6:52 AM
*To:* OpenSplice DDS Developer Mailing List
*Subject:* [OSPL-Dev] bi directional communication between publisher
andsubscriber
hi all,
I wanted to know whether bi-directional communication is possible in
opensplice DDS between a publisher and subscriber or not.. Or do we have to
integrate both publisher and subscriber code at both the ends
to fulfill it?
--
Thanks & Regards
Ravi
_______________________________________________
OpenSplice DDS Developer Mailing List
Developer at opensplice.org
Subscribe / Unsubscribe
http://dev.opensplice.org/mailman/listinfo/developer
--
Thanks & Regards
Ravi
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://dev.opensplice.org/pipermail/developer/attachments/20110712/e3b6d20f/attachment.htm>
Loading...