![]() |
Telelogic Rhapsody (steve huntington) | ![]() |
Topic Title: New "distributed" version of Bluetooth Headset Topic Summary: Created On: 24-Jan-2006 18:07 Status: Read Only |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|||
Here is a new version of the C++ Bluetooth Headset that allows the Headset and MobilePhone to run as separate components communicating via a number of different mechanisms such as:
[list] [*]CORBA ( Uses TAO ) [*]COM [*]VxWorks Message Channels ( works between RTP's ) [*]INTEGRITY Connections ( Uses a VB macro to generate the integrate file ) [*]Shared Memory [*]QNX Messages [/list] Please note:I have not yet got the QNX processes to communicate yet. Similarly I have the COM version working, but only in one direction.
|
|||
![]() |
|||
![]() |
|||
Hi Mark,
this is a really nice example which I learnt a lot from about setting up many variants in one project. But I was a bit disappointed because I had hoped that also the code from the CORBA webinar would be included: Since I watched the CORBA webinar, I am curious what's behind the "CORBA Link" stereotype which was used there on a link between the ports of two distributed objects. My Rhapsody 6.1MR1 doesn't offer such a stereotype! What's the secret behind that? As I understand it, your example above doesn't use ports, but simple associations to CORBA-link the distributed components. Can you educate me in this matter? Thanks in advance, Thomas |
|||
![]() |
|||
![]() |
|||
Hi,
I'm glad to see that it's been useful. As for the CORBA "Link" this is something that a colleague added to denote a link between 2 CORBA ports. I believe that he had a macro that checked for this and auto generated some utility functions. Regards, Mark.
|
|||
![]() |
|||
![]() |
|||
:-) Perhaps that colleague would share the macro with us? :-)
Thomas |
|||
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.