Hi devs,
Here is a patch that adds a new operation to the Deployer to be able to
connect two operations.
Formerly, the deployer could only connect services, with the assumption
that required and provided operations had the same name.
This new method allows to connect any provided operation to any required
operation, if this connection is valid of course.
For instance:
connectOperations("A.requestedOperation", "B.myService.providedOp")
Charles.
| Attachment | Size |
|---|---|
| 0001-Deployer-add-a-connectOperation-method.patch | 8.9 KB |
New 'connectOperations' operation in the Deployer
Hi Charles,
On Thu, Jul 5, 2012 at 10:44 AM, Charles Lesire-Cabaniols <
charles [dot] lesire [..] ...> wrote:
> Hi devs,
>
> Here is a patch that adds a new operation to the Deployer to be able to
> connect two operations.
>
> Formerly, the deployer could only connect services, with the assumption
> that required and provided operations had the same name.
>
> This new method allows to connect any provided operation to any required
> operation, if this connection is valid of course.
> For instance:
>
> connectOperations("A.requestedOperation", "B.myService.providedOp")
>
>
Thanks, I applied it to master and pushed it to gitorious.
Peter
New 'connectOperations' operation in the Deployer
On Fri, Jul 6, 2012 at 1:24 PM, Peter Soetens <peter [..] ...> wrote:
> Hi Charles,
>
> On Thu, Jul 5, 2012 at 10:44 AM, Charles Lesire-Cabaniols
> <charles [dot] lesire [..] ...> wrote:
>>
>> Hi devs,
>>
>> Here is a patch that adds a new operation to the Deployer to be able to
>> connect two operations.
>>
>> Formerly, the deployer could only connect services, with the assumption
>> that required and provided operations had the same name.
>>
>> This new method allows to connect any provided operation to any required
>> operation, if this connection is valid of course.
>> For instance:
>>
>> connectOperations("A.requestedOperation", "B.myService.providedOp")
>
>
> Thanks, I applied it to master and pushed it to gitorious.
Is there any chance that this would endup in toolchain-2.5?
> Peter
Ruben
>
> --
> Orocos-Dev mailing list
> Orocos-Dev [..] ...
> http://lists.mech.kuleuven.be/mailman/listinfo/orocos-dev
>
New 'connectOperations' operation in the Deployer
On Thu, Jul 26, 2012 at 12:56 PM, Ruben Smits
<ruben [dot] smits [..] ...> wrote:
> On Fri, Jul 6, 2012 at 1:24 PM, Peter Soetens <peter [..] ...> wrote:
>> Hi Charles,
>>
>> On Thu, Jul 5, 2012 at 10:44 AM, Charles Lesire-Cabaniols
>> <charles [dot] lesire [..] ...> wrote:
>>>
>>> Hi devs,
>>>
>>> Here is a patch that adds a new operation to the Deployer to be able to
>>> connect two operations.
>>>
>>> Formerly, the deployer could only connect services, with the assumption
>>> that required and provided operations had the same name.
>>>
>>> This new method allows to connect any provided operation to any required
>>> operation, if this connection is valid of course.
>>> For instance:
>>>
>>> connectOperations("A.requestedOperation", "B.myService.providedOp")
>>
>>
>> Thanks, I applied it to master and pushed it to gitorious.
>
> Is there any chance that this would endup in toolchain-2.5?
No, otherwise I would have applied it on that branch directly.
Peter