btgoodwin
commented
3 years ago There are several ways to do this depending on what you're trying to do. The most simple thing is to use statements from that other issue's comments to attach to both domains, iterate to the associated components/devices and connect them (comp.connect(remote_comp)). Aside from that, here are a couple more options:
If you're trying to send small structured messages between the components running in different domains, you could build a bridge component (or device or service) that implements some other protocol like ZMQ on its own socket server. You would then connect those two components using whatever the underlying socket server requires and let that entity (component/device/service) handle the translation from MessageEvent (for example) to whatever structure the protocol requires and back again. This is a lot like how the github.com/geontech/rest-python server works when egressing events to a UI over a websocket.
If you're wanting to arbitrarily connect ports together, you can resolve the remote object's OmniNames IOR to a core framework object at the destination. For example in the python shell:
# at the source
from ossie.utils import redhawk
dom = redhawk.attach()
# iterate to the component, comp
remote_component_ior = dom.orb.object_to_string(comp.ref)By some means you would convey that IOR information to the destination environment which could do something similar to this:
# at the destination
from ossie.cf import CF
from ossie.utils import redhawk
dom = redhawk.attach()
remote_comp_ref = dom.orb.string_to_object(remote_component_ior)
remote_comp = remote_comp_ref.narrow(CF.Component)
remote_comp.api()Using statements from the other issue, you can see how one can code up a python script that runs only in one location to setup these kinds of connections by attaching to both the local and remote domains, which brings me back to the first couple of statements about the "most simple route". The last example is really just showcasing that even though there is a single omniNames service for a Domain, it doesn't actually make the Domain and its contents an island.
NayanaAnand
Hi all,
I am trying to interact between 2 Hardware which are loaded with Yocto image(built with meta-redhawk-sdr layer). OmniNames, OmniEvents, Domain and Device managers are able to run on Hardware.
Requirement : On each Hardware launched Redhawk components using sandbox and is there any ways to interact between those components which is running on different Hardware?
Regards, Nayana