NCS: Message Transfer Systems - Revision history

Murray: /* Additional Resources */

2006-04-03T05:14:49Z

Additional Resources

← Older revision		Revision as of 05:14, 3 April 2006
Line 18:		Line 18:
	* [http://www.isd.mel.nist.gov/projects/rcslib/NMLcpp.html Neutral Message Language (NML) Programmers Guide] - part of the NIST [http://www.isd.mel.nist.gov/projects/rcslib/ Realtime Control System] library		* [http://www.isd.mel.nist.gov/projects/rcslib/NMLcpp.html Neutral Message Language (NML) Programmers Guide] - part of the NIST [http://www.isd.mel.nist.gov/projects/rcslib/ Realtime Control System] library
	* [http://roboflag.mae.cornell.edu/Documentation.html RoboFlag documentation] - includes discussion of how RoboFlag network communications are implemented		* [http://roboflag.mae.cornell.edu/Documentation.html RoboFlag documentation] - includes discussion of how RoboFlag network communications are implemented


	== Project Ideas==		== Project Ideas==
	* Modify the Spread protocol such that it can deal with the following situation. For typical control applications, most recent data is more important than the old data. Imagine that a process needs three packets, m1, m2 and m3, where m1 is older than m2 and m2 is older than m3. Suppose that m2 is missing, then the process should '''only''' request for this packet on the condition that m3 is not received yet. Current version of Spread has not addressed this issue yet.		* Modify the Spread protocol such that it can deal with the following situation. For typical control applications, most recent data is more important than the old data. Imagine that a process needs three packets, m1, m2 and m3, where m1 is older than m2 and m2 is older than m3. Suppose that m2 is missing, then the process should '''only''' request for this packet on the condition that m3 is not received yet. Current version of Spread has not addressed this issue yet.

Shiling: /* Project Ideas */

2006-04-03T05:03:02Z

Project Ideas

← Older revision		Revision as of 05:03, 3 April 2006
Line 21:		Line 21:

	== Project Ideas==		== Project Ideas==
	* Modify the Spread protocol such that it can deal with the following situation. For typical control applications, most recent data is more important than the old data. ~~Suppose~~ that a process needs three packets, m1, m2 and m3, where m1 is older than m2 and m2 is older than m3. Suppose that m2 is missing, then the process should '''only''' request for this packet on the condition that m3 is not received yet. Current version of Spread has not addressed this issue yet.		* Modify the Spread protocol such that it can deal with the following situation. For typical control applications, most recent data is more important than the old data. Imagine that a process needs three packets, m1, m2 and m3, where m1 is older than m2 and m2 is older than m3. Suppose that m2 is missing, then the process should '''only''' request for this packet on the condition that m3 is not received yet. Current version of Spread has not addressed this issue yet.

Shiling: /* Project Ideas */

2006-04-03T05:02:23Z

Project Ideas

← Older revision		Revision as of 05:02, 3 April 2006
Line 21:		Line 21:

	== Project Ideas==		== Project Ideas==
	*		* Modify the Spread protocol such that it can deal with the following situation. For typical control applications, most recent data is more important than the old data. Suppose that a process needs three packets, m1, m2 and m3, where m1 is older than m2 and m2 is older than m3. Suppose that m2 is missing, then the process should '''only''' request for this packet on the condition that m3 is not received yet. Current version of Spread has not addressed this issue yet.

Shiling at 04:55, 3 April 2006

2006-04-03T04:55:59Z

← Older revision		Revision as of 04:55, 3 April 2006
Line 18:		Line 18:
	* [http://www.isd.mel.nist.gov/projects/rcslib/NMLcpp.html Neutral Message Language (NML) Programmers Guide] - part of the NIST [http://www.isd.mel.nist.gov/projects/rcslib/ Realtime Control System] library		* [http://www.isd.mel.nist.gov/projects/rcslib/NMLcpp.html Neutral Message Language (NML) Programmers Guide] - part of the NIST [http://www.isd.mel.nist.gov/projects/rcslib/ Realtime Control System] library
	* [http://roboflag.mae.cornell.edu/Documentation.html RoboFlag documentation] - includes discussion of how RoboFlag network communications are implemented		* [http://roboflag.mae.cornell.edu/Documentation.html RoboFlag documentation] - includes discussion of how RoboFlag network communications are implemented


			== Project Ideas==
			*

Shiling: /* Reading */

2006-04-03T04:54:10Z

Reading

← Older revision		Revision as of 04:54, 3 April 2006
Line 12:		Line 12:
	* <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 a detailed technical description of how [[Spread]] works. It is mainly useful if you want to know more about what [[spread]] does. Requires some background in network protocols if you want to understand the details. </p>		* <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 a detailed technical description of how [[Spread]] works. It is mainly useful if you want to know more about what [[spread]] does. Requires some background in network protocols if you want to understand the details. </p>

	* <p>[http://www.cnds.jhu.edu/pub/papers/hop_ftcs2000.pdf		* <p>[http://www.cnds.jhu.edu/pub/papers/hop_ftcs2000.pdf A Low Latency, Loss Tolerant Architecture and Protocol for Wide Area Group Communication], Yair Amir, Claudiu Danilov, and Jonathan Stanton. International Conference on Dependable Systems and Networks (DSN00), New York, New York, June 25-28, 2000. The paper is similar to the one above but with more technical details. </p>
	A Low Latency, Loss Tolerant Architecture and Protocol for Wide Area Group Communication], Yair Amir, Claudiu Danilov, and Jonathan Stanton. International Conference on Dependable Systems and Networks (DSN00), New York, New York, June 25-28, 2000. The paper is similar to the one above but with more technical details. </p>

	== Additional Resources ==		== Additional Resources ==

Shiling: /* Reading */

2006-04-03T04:53:44Z

Reading

← Older revision		Revision as of 04:53, 3 April 2006
Line 11:		Line 11:
	*<p>[http://www.spread.org/docs/guide/users_guide.pdf A Users Guide to Spread], J. Stanton. 2002. This is the documentation for the [http://www.spread.org Spread Toolkit]. The first and second chapters provide most of the information you need to understand the basic ideas, although the way in which [[Spread]] servers are configured, described in Chapter 3, is also useful.</p>		*<p>[http://www.spread.org/docs/guide/users_guide.pdf A Users Guide to Spread], J. Stanton. 2002. This is the documentation for the [http://www.spread.org Spread Toolkit]. The first and second chapters provide most of the information you need to understand the basic ideas, although the way in which [[Spread]] servers are configured, described in Chapter 3, is also useful.</p>
	* <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 a detailed technical description of how [[Spread]] works. It is mainly useful if you want to know more about what [[spread]] does. Requires some background in network protocols if you want to understand the details. </p>		* <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 a detailed technical description of how [[Spread]] works. It is mainly useful if you want to know more about what [[spread]] does. Requires some background in network protocols if you want to understand the details. </p>

			* <p>[http://www.cnds.jhu.edu/pub/papers/hop_ftcs2000.pdf
			A Low Latency, Loss Tolerant Architecture and Protocol for Wide Area Group Communication], Yair Amir, Claudiu Danilov, and Jonathan Stanton. International Conference on Dependable Systems and Networks (DSN00), New York, New York, June 25-28, 2000. The paper is similar to the one above but with more technical details. </p>

	== Additional Resources ==		== Additional Resources ==

Murray: /* Reading */

2006-04-01T04:19:13Z

Reading

← Older revision		Revision as of 04:19, 1 April 2006
Line 7:		Line 7:

	== Reading ==		== Reading ==
	* <p>Missing. I'm still looking for a good reference on causality and message passing.</p>		* <p>[http://portal.acm.org/citation.cfm?id=359563 Time, clocks, and the ordering of events in a distributed system], L. Lamport. ''Communications of the ACM'', 21(7):558-565, 1978. This is a classic paper on ordering of messages in distributed systems. A must read for distributed systems. </p>
	* <p>[http://portal.acm.org/citation.cfm?id=359563 Time, clocks, and the ordering of events in a distributed system], L. Lamport. ''Communications of the ACM'', 21(7):558-565, 1978. This is a classic paper on ordering of messages in distributed systems. </p>
	* <p>[http://portal.acm.org/citation.cfm?coll=GUIDE&dl=GUIDE&id=37515 Exploiting virtual synchrony in distributed systems], K. Birman and T. Joseph. ACM Symposium on Operating Systems Principles, 1987. This paper gives a nice overview of some of the problems in group messaging systems and is one of the sets of papers that motivated the work that lead to [[Spread]].</p>		* <p>[http://portal.acm.org/citation.cfm?coll=GUIDE&dl=GUIDE&id=37515 Exploiting virtual synchrony in distributed systems], K. Birman and T. Joseph. ACM Symposium on Operating Systems Principles, 1987. This paper gives a nice overview of some of the problems in group messaging systems and is one of the sets of papers that motivated the work that lead to [[Spread]].</p>
	*<p>[http://www.spread.org/docs/guide/users_guide.pdf A Users Guide to Spread], J. Stanton. 2002. This is the documentation for the [http://www.spread.org Spread Toolkit]. The first and second chapters provide most of the information you need to understand the basic ideas, although the way in which [[Spread]] servers are configured, described in Chapter 3, is also useful.</p>		*<p>[http://www.spread.org/docs/guide/users_guide.pdf A Users Guide to Spread], J. Stanton. 2002. This is the documentation for the [http://www.spread.org Spread Toolkit]. The first and second chapters provide most of the information you need to understand the basic ideas, although the way in which [[Spread]] servers are configured, described in Chapter 3, is also useful.</p>

Murray: /* Lecture Materials */

2006-03-31T18:12:23Z

Lecture Materials

← Older revision		Revision as of 18:12, 31 March 2006
Line 4:		Line 4:

	== Lecture Materials ==		== Lecture Materials ==
	* [[Media:L1-~~1_mta~~.pdf\|Lecture: Message Transfer ~~Architectures~~]]		* [[Media:L1-3_spread.pdf\|Lecture: Message Transfer Systems]]

	== Reading ==		== Reading ==

Murray: /* Reading */

2006-03-30T19:02:56Z

Reading

← Older revision		Revision as of 19:02, 30 March 2006
Line 9:		Line 9:
	* <p>Missing. I'm still looking for a good reference on causality and message passing.</p>		* <p>Missing. I'm still looking for a good reference on causality and message passing.</p>
	* <p>[http://portal.acm.org/citation.cfm?id=359563 Time, clocks, and the ordering of events in a distributed system], L. Lamport. ''Communications of the ACM'', 21(7):558-565, 1978. This is a classic paper on ordering of messages in distributed systems. </p>		* <p>[http://portal.acm.org/citation.cfm?id=359563 Time, clocks, and the ordering of events in a distributed system], L. Lamport. ''Communications of the ACM'', 21(7):558-565, 1978. This is a classic paper on ordering of messages in distributed systems. </p>
	* <p>[p://portal.acm.org/citation.cfm?coll=GUIDE&dl=GUIDE&id=37515 Exploiting virtual synchrony in distributed systems], K. Birman and T. Joseph. ACM Symposium on Operating Systems Principles, 1987.</p>		* <p>[http://portal.acm.org/citation.cfm?coll=GUIDE&dl=GUIDE&id=37515 Exploiting virtual synchrony in distributed systems], K. Birman and T. Joseph. ACM Symposium on Operating Systems Principles, 1987. This paper gives a nice overview of some of the problems in group messaging systems and is one of the sets of papers that motivated the work that lead to [[Spread]].</p>
	*<p>[http://www.spread.org/docs/guide/users_guide.pdf A Users Guide to Spread], J. Stanton. 2002. This is the documentation for the [http://www.spread.org Spread Toolkit]. The first and second chapters provide most of the information you need to understand the basic ideas, although the way in which [[Spread]] servers are configured, described in Chapter 3, is also useful.</p>		*<p>[http://www.spread.org/docs/guide/users_guide.pdf A Users Guide to Spread], J. Stanton. 2002. This is the documentation for the [http://www.spread.org Spread Toolkit]. The first and second chapters provide most of the information you need to understand the basic ideas, although the way in which [[Spread]] servers are configured, described in Chapter 3, is also useful.</p>
	* <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 a detailed technical description of how [[Spread]] works. It is mainly useful if you want to know more about what [[spread]] does. Requires some background in network protocols if you want to understand the details. </p>		* <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 a detailed technical description of how [[Spread]] works. It is mainly useful if you want to know more about what [[spread]] does. Requires some background in network protocols if you want to understand the details. </p>

Murray: /* Reading */

2006-03-30T17:58:07Z

Reading

← Older revision		Revision as of 17:58, 30 March 2006
Line 9:		Line 9:
	* <p>Missing. I'm still looking for a good reference on causality and message passing.</p>		* <p>Missing. I'm still looking for a good reference on causality and message passing.</p>
	* <p>[http://portal.acm.org/citation.cfm?id=359563 Time, clocks, and the ordering of events in a distributed system], L. Lamport. ''Communications of the ACM'', 21(7):558-565, 1978. This is a classic paper on ordering of messages in distributed systems. </p>		* <p>[http://portal.acm.org/citation.cfm?id=359563 Time, clocks, and the ordering of events in a distributed system], L. Lamport. ''Communications of the ACM'', 21(7):558-565, 1978. This is a classic paper on ordering of messages in distributed systems. </p>
			* <p>[p://portal.acm.org/citation.cfm?coll=GUIDE&dl=GUIDE&id=37515 Exploiting virtual synchrony in distributed systems], K. Birman and T. Joseph. ACM Symposium on Operating Systems Principles, 1987.</p>
	*<p>[http://www.spread.org/docs/guide/users_guide.pdf A Users Guide to Spread], J. Stanton. 2002. This is the documentation for the [http://www.spread.org Spread Toolkit]. The first and second chapters provide most of the information you need to understand the basic ideas, although the way in which [[Spread]] servers are configured, described in Chapter 3, is also useful.</p>		*<p>[http://www.spread.org/docs/guide/users_guide.pdf A Users Guide to Spread], J. Stanton. 2002. This is the documentation for the [http://www.spread.org Spread Toolkit]. The first and second chapters provide most of the information you need to understand the basic ideas, although the way in which [[Spread]] servers are configured, described in Chapter 3, is also useful.</p>
	* <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 a detailed technical description of how [[Spread]] works. It is mainly useful if you want to know more about what [[spread]] does. Requires some background in network protocols if you want to understand the details. </p>		* <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 a detailed technical description of how [[Spread]] works. It is mainly useful if you want to know more about what [[spread]] does. Requires some background in network protocols if you want to understand the details. </p>