NCS: Message Transfer Systems: Difference between revisions
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
{{cds270-2 header}} <!-- Generates the header, including table of contents and link back to main page --> | {{cds270-2 header}} <!-- Generates the header, including table of contents and link back to main page --> | ||
This lecture describes different choices for ''message transfer systems'' in a networked control system. The message transfer system is responsible for managing network communications between computers and software modules with the control system. We focus on systems that are build on top of the TCP/IP protocol stack. Design choices include how to encode information in packets, whether to broadcast or send packets point-to-point, and whether to retransmit packets on lost data transmission. Because of the closed loop nature of the networked embedded systems that we are programming, timing and latency are critical issues. We focus on the use of [[spread]] as a specific example of a low-level message transfer subsystem and describe how it can be used in a NCS context. | |||
== Lecture Materials == | == Lecture Materials == | ||
* [[Media:L1-1_mta.pdf|Lecture: Message Transfer Architectures]] | |||
== Reading == | == Reading == | ||
< | * <p>[http://www.cnds.jhu.edu/pub/papers/spread.pdf The Spread Wide Area Group Communication System], Y. Amir and J. Stanton. | ||
Technical Report CNDS-98-4, The Center for Networking and Distributed Systems, The Johns Hopkins University, 1998. The paper provides an overview of the [http://www.spread.org Spread Toolkit], which provides a simple mechanism for networked communications.</p> | |||
== Additional Resources == | == Additional Resources == | ||
<!-- Links to additional information. If there are good sources of additional information for students interested in exploring this topic further, these should go at the bottom of the page. --> | <!-- Links to additional information. If there are good sources of additional information for students interested in exploring this topic further, these should go at the bottom of the page. --> | ||
Revision as of 03:40, 26 March 2006
| Prev: Alice Intro | Course Home | Next: Pthreads |
This lecture describes different choices for message transfer systems in a networked control system. The message transfer system is responsible for managing network communications between computers and software modules with the control system. We focus on systems that are build on top of the TCP/IP protocol stack. Design choices include how to encode information in packets, whether to broadcast or send packets point-to-point, and whether to retransmit packets on lost data transmission. Because of the closed loop nature of the networked embedded systems that we are programming, timing and latency are critical issues. We focus on the use of spread as a specific example of a low-level message transfer subsystem and describe how it can be used in a NCS context.
Lecture Materials
Reading
The Spread Wide Area Group Communication System, Y. Amir and J. Stanton.
Technical Report CNDS-98-4, The Center for Networking and Distributed Systems, The Johns Hopkins University, 1998. The paper provides an overview of the Spread Toolkit, which provides a simple mechanism for networked communications.
