draft #69
Link / noReturnTraffic
| Status: | submitted | Start date: | 03/21/2013 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | - | % Done: | 0% |
|
| Category: | - | |||
| Target version: | - |
Description
The current description of the noReturnTraffic parameter of a Link is somewhat cryptic:
noReturnTraffic. A value of true changes the definition of Link to: data transport from each sources to all sinks, except that there is no data transport from a source to a sink if the source and sink are grouped together in a BidirectionalPort group. The default value of noReturnTraffic is false.
This should be updated to explain better what it means.
History
Updated by Jeroen van der Ham over 9 years ago
A proposal is to add the following:
An example of where this is used is in an Ethernet broadcast domain, where broadcast traffic is sent to all sinks, except the sink Port associated with the sending source Port.
Perhaps extend this even more:
An example of where this is used is in an Ethernet broadcast domain, which would be modelled using one Link object with many source and sink Ports. Defining noReturnTraffic=true would model that broadcast traffic is sent to all sinks, except the sink Port associated with the sending source Port.
(Other formats not available in this archive.