AutoConnect, Peers and Services

Hi

I would like to know if the following statemetn is trrue:

Peers is useless outside of the context of autoconnect BUT they might
be used in services?

-H

AutoConnect, Peers and Services

On Wednesday 15 December 2010 11:43:22 Hugo Garcia wrote:
> Hi
>
> I would like to know if the following statemetn is trrue:
>
> Peers is useless outside of the context of autoconnect BUT they might
> be used in services?

It's not *might*, it's *are*. Adding a component as a peer allows one
component to use the service interface of another, for example, 'A' can call
an operation of 'B' if B is a peer of A.

Read 'peer' as 'having a pointer (or reference) to'.

Peter

AutoConnect, Peers and Services

On Wed, Dec 15, 2010 at 11:51, Peter Soetens <peter [..] ...> wrote:
> On Wednesday 15 December 2010 11:43:22 Hugo Garcia wrote:
>> Hi
>>
>> I would like to know if the following statemetn is trrue:
>>
>> Peers is useless outside of the context of autoconnect BUT they might
>> be used in services?
>
> It's not *might*, it's *are*. Adding a component as a peer allows one
> component to use the service interface of another, for example, 'A' can call
> an operation of 'B' if B is a peer of A.
>
> Read 'peer' as 'having a pointer (or reference) to'.
>
> Peter
>

Ah, so... given two components that have no ports but do offer
services: then graphically we could use a link between them in order
to establish and denote that they are peers.

This would fit nicely with the "deployment activity" of selecting
autoconnect for those peers that are linked int he graphical editor
while ALSO providing support for services where peers are defined but
not autoconnected.

-H

-H