Bugzilla – Full Text Bug Listing
| Summary: | Introduction of Composite Protocols | ||
|---|---|---|---|
| Product: | [Modeling] eTrice | Reporter: | Henrik Rentz-Reichert <hrr> |
| Component: | Core | Assignee: | Project Inbox <etrice.core-inbox> |
| Status: | CLOSED DUPLICATE | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | ||
| Version: | 0.1.0 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
Marked as duplicate *** This bug has been marked as a duplicate of bug 382440 *** Part of eTrice 0.2 |
A new modeling element is proposed, the CompositeProtocolClass: CompositeProtocolClass: 'CompositeProtocolClass' '{' (protocolRefs+=ProtocolRef)* '}'; ProtocolRef: 'ProtocolRef' name=ID protocol=[ProtocolClass|FQN] A Composite Protocol is just the union of the referenced protocols, i.e. all incoming messages and all outgoing ones. A port of a Composite Protocol can be connected multiply where the peer ports match the protocols referenced by the composite. In this role the Composite Protocol port works as a multiplexer/demultiplexer. The demultiplexing is controlled by binding names (to be introduced) matching the reference names in the Composite Protocol.