On Tuesday April 29 2008 09:33:40 Peter Soetens wrote:
> On Monday 28 April 2008 20:29:10 Ruben Smits wrote:
> > Maybe the deployer should also offer the opposite:
> >
> > creating a CorbaServer of a component loaded by the deployer, so remote
> > tasks can connect to it?
>
> It already does so indirectly. The 'cdeployer-target' is itself a
> ControlTaskServer, which causes each component connected to it (and browsed
> [*]) become a ControlTaskServer as well. The new 'deployer-corba-target'
> does the same, but also provides the taskbrowser text interface. This patch
> did not extend the standard, non-CORBA 'deployer-target' application.
>
> However,
> [*] We could drop the 'browsed' requirement with a propertyi or so such that
> you don't have to find each networked component through the Deployer. So
> the patch is indeed not yet perfect.

I'm more interested in this approach, because i think there is a difference
between remotely connecting to a complete application or connecting to a
single component.

Imagine i have an application of 20 components, and i want to remotely connect
with only 2 or 3, each of them from a different place (e.g. for visualisation
of my robot or monitoring of a controller). Then i don't want to deploy all
my components over CORBA.

Ruben