Migration of the service_discovery package into orocos-toolchain

For a long time now, orogen-generated deployments know how to publish
the components on zeroconf. To achieve this, they require a separate
package (look for tools/service_discovery in on rock-robotics.org).

Since I am synchronizing the orocos toolchain packages with rock, I am
now faced with the following two options:

- add service_discovery to the toolchain, and keep it an optional
dependency for orogen
- remove the dependency. The functionality will still be there (since
it is optional)

Opinions ?

Migration of the service_discovery package into orocos-toolchain

Hi Sylvain,

On Sat, Sep 29, 2012 at 11:07 AM, Sylvain Joyeux <sylvain [dot] joyeux [..] ...> wrote:
> For a long time now, orogen-generated deployments know how to publish
> the components on zeroconf. To achieve this, they require a separate
> package (look for tools/service_discovery in on rock-robotics.org).
>
> Since I am synchronizing the orocos toolchain packages with rock, I am
> now faced with the following two options:
>
> - add service_discovery to the toolchain, and keep it an optional
> dependency for orogen
> - remove the dependency. The functionality will still be there (since
> it is optional)
>
> Opinions ?

I'm definately in favour for a corba-independent directory service, if
this is what it is... or does it only publish corba endpoints ?

Peter

Migration of the service_discovery package into orocos-toolchain

On 09/29/2012 05:31 PM, Peter Soetens wrote:
> Hi Sylvain,
>
> On Sat, Sep 29, 2012 at 11:07 AM, Sylvain Joyeux<sylvain [dot] joyeux [..] ...> wrote:
>> For a long time now, orogen-generated deployments know how to publish
>> the components on zeroconf. To achieve this, they require a separate
>> package (look for tools/service_discovery in on rock-robotics.org).
>>
>> Since I am synchronizing the orocos toolchain packages with rock, I am
>> now faced with the following two options:
>>
>> - add service_discovery to the toolchain, and keep it an optional
>> dependency for orogen
>> - remove the dependency. The functionality will still be there (since
>> it is optional)
>>
>> Opinions ?
>
> I'm definately in favour for a corba-independent directory service, if
> this is what it is... or does it only publish corba endpoints ?
It publishes CORBA IORs. But since CORBA is the only way one can access
RTT components remotely, that's the only option.