Hi!

There was a question about new disconnect and unmap
operations, and I would like to give my comments.

> Currently, UNMAP and DISCONNECT are applicable to one connection
> only, i.e., you have to specify the endpoints (component references
> and port names) of a specific connection.
>
> The proposal is to extend this by e.g., allowing
> DISCONNECT(myComponent)
> which will release all connections of component myComponent or
> ALL PORT.UNMAP which will unmap all ports of all components.

The TTCN-3 language already contains inter test component communication
mechanism, i.e. the connecting ports between two test components
and sending messages or making calls between these components.

If some kind of more powerful disconnection mechanism is actually
needed (I don't have information about that kind of need), I think,
that it could be provided in the form of disconnecting or unmapping
all the ports of one component, i.e. of the component where that
statement is executed.

So if unmap and disconnect are modified, please only consider
versions that would affect all the ports within one component.

In my opinion, adding statements that combine communication between
test components and operations executed in test components adds
complexity that should not be done without good reasons.

It would be also good to keep some kind of encapsulation of the
effects of the statements, so that communication between the
component would be kept separate from the behavior of the
components. Usually this idea is regarded beneficial in
Object Oriented models.

Best regards,
Vesa-Matti

--
Vesa-Matti Puro
E-mail: This email address is being protected from spambots. You need JavaScript enabled to view it.
Tel.: +358 440396461
OpenTTCN Oy
Web: www.openttcn.com