Welcome, Guest
Username: Password: Remember me
  • Page:
  • 1

TOPIC: System ports

System ports 02 Aug 2004 12:17 #6743

Hi,

Assume I have a system component with two ports:

* Is it legal to let both ports accept in-messages of the same
type (or even to let the system component have two instances of the same port
type)?
* In case it is legal, should a message that matches the common
type be inserted into both ports or is the behavior undefined?


Best regards,

Stefan Karlsson
The administrator has disabled public write access.

System ports 03 Aug 2004 05:58 #6744

ext Stefan Karlsson wrote:

> Hi,
>
> Assume I have a/ system/ component with two ports:
>
> * Is it legal to let both ports accept in-messages of the same
> type (or even to let the system component have two instances of
> the same port type)?
>

Yes.

> * In case it is legal, should a message that matches the common
> type be inserted into both ports or is the behavior undefined?
>

It should only be inserted into one port queue. Which one that is, will depend
on your SA implementation and the purposes of your ports. If the SA cannot
figure out, to which port the message _really_ belongs, then I guess you
modelling of the interfaces is off and you should only have a single port.

Also, remember that decoding of messages (and hence checking of which type a
message is) takes place only _after_ the message has been inserted into the port
queue. Of course, nobody will stop you from running a decoder in your SA, but
that is certainly not the canonical way of doing things.

Regards

Stephan Tobies

--
Stephan Tobies Sr. Research Engineer, Nokia Research Center
~ Mobile Networks Lab, Protocol Engineering Group
E-Mail: This email address is being protected from spambots. You need JavaScript enabled to view it.
Work Phone: +49-234-9842262
Mobile: +49-163-9842405
Fax: +49-234-9843491
Address: NRC Bochum, Meesmannstr. 103, 44807 Bochum, Germany
The administrator has disabled public write access.

System ports 03 Aug 2004 06:54 #6745

Hi,

Yes, it is legal.

The behaviour is determined by the implementation of the System Adapter.
The SA needs to call triEnqueueMsg with the component, that should receive the
message.

Regards,
Matthias Jung
--
See the Newest Innovations in Requirements Management.
Learn more about DOORS 7.1 at www.telelogic.com


Dr. Matthias Jung
Application Development
Telelogic Deutschland GmbH, Otto-Brenner-Str. 247 , 33604 Bielefeld, Germany
Phone: +49(521)14503-33
Fax: +49(521)14503-50
Mail: This email address is being protected from spambots. You need JavaScript enabled to view it.

Telelogic - Requirements-Driven Innovation.

The information contained in this e-mail, including any attachment or
enclosure, is intended only for the person or entity to which it is addressed
and may contain confidential material. Any unauthorised use, review,
retransmissions, dissemination, copying or other use of this information by
persons or entities other than the intended recipient is prohibited.

Original Message
From: active_ttcn3 : mts stf133 ttcn version 3 - active members only
[This email address is being protected from spambots. You need JavaScript enabled to view it.]
Sent: Monday, August 02, 2004 2:18 PM
To: This email address is being protected from spambots. You need JavaScript enabled to view it.
Subject: System ports


Hi,
Assume I have a system component with two ports:
Is it legal to let both ports accept in-messages of the same type (or even to
let the system component have two instances of the same port type)?
In case it is legal, should a message that matches the common type be inserted
into both ports or is the behavior undefined?


Best regards,
Stefan Karlsson
The administrator has disabled public write access.
  • Page:
  • 1

FacebookTwitterGoogle BookmarksRedditNewsvineTechnoratiLinkedin