CSC/ECE 517 Fall 2012/ch2b 2w45 pg - Revision history

Pwu6: /* Command pattern on MSDN Microsoft Website */

2012-11-20T03:46:54Z

Command pattern on MSDN Microsoft Website

← Older revision		Revision as of 03:46, 20 November 2012
Line 57:		Line 57:

	The distributed command system discussed here is the combination of reliable messaging, services, and the Command pattern. While most often seen as a design pattern for implementing desktop application menu systems, the Command pattern offers advantages for distributed systems when combined with a robust messaging infrastructure like MSMQ.		The distributed command system discussed here is the combination of reliable messaging, services, and the Command pattern. While most often seen as a design pattern for implementing desktop application menu systems, the Command pattern offers advantages for distributed systems when combined with a robust messaging infrastructure like MSMQ.

			[[File:4.gif]]

	<b>Learning: </b><br>		<b>Learning: </b><br>

Pwu6: /* Command pattern on MSDN Microsoft Website */

2012-11-20T03:43:50Z

Command pattern on MSDN Microsoft Website

← Older revision		Revision as of 03:43, 20 November 2012
Line 54:		Line 54:
	• But generally the participants are hybrid and they don't share a common platform, in such situations service oriented architecture comes handy. Here the requests are queued in Microsoft Message Queuing (MSMQ) which implements Command design pattern.		• But generally the participants are hybrid and they don't share a common platform, in such situations service oriented architecture comes handy. Here the requests are queued in Microsoft Message Queuing (MSMQ) which implements Command design pattern.

	[[File:3.~~jpg~~]]		[[File:3.gif]]

	The distributed command system discussed here is the combination of reliable messaging, services, and the Command pattern. While most often seen as a design pattern for implementing desktop application menu systems, the Command pattern offers advantages for distributed systems when combined with a robust messaging infrastructure like MSMQ.		The distributed command system discussed here is the combination of reliable messaging, services, and the Command pattern. While most often seen as a design pattern for implementing desktop application menu systems, the Command pattern offers advantages for distributed systems when combined with a robust messaging infrastructure like MSMQ.

Pwu6: /* Command pattern on MSDN Microsoft Website */

2012-11-20T03:43:10Z

Command pattern on MSDN Microsoft Website

← Older revision		Revision as of 03:43, 20 November 2012
Line 54:		Line 54:
	• But generally the participants are hybrid and they don't share a common platform, in such situations service oriented architecture comes handy. Here the requests are queued in Microsoft Message Queuing (MSMQ) which implements Command design pattern.		• But generally the participants are hybrid and they don't share a common platform, in such situations service oriented architecture comes handy. Here the requests are queued in Microsoft Message Queuing (MSMQ) which implements Command design pattern.

	[[File:~~http://i~~.~~msdn.microsoft.com/cc163920.fig02(en-us).gif~~]]		[[File:3.jpg]]

	The distributed command system discussed here is the combination of reliable messaging, services, and the Command pattern. While most often seen as a design pattern for implementing desktop application menu systems, the Command pattern offers advantages for distributed systems when combined with a robust messaging infrastructure like MSMQ.		The distributed command system discussed here is the combination of reliable messaging, services, and the Command pattern. While most often seen as a design pattern for implementing desktop application menu systems, the Command pattern offers advantages for distributed systems when combined with a robust messaging infrastructure like MSMQ.

Pwu6: /* Introduction */

2012-11-20T03:41:56Z

Introduction

← Older revision		Revision as of 03:41, 20 November 2012
Line 24:		Line 24:
	Using command objects makes it easier to construct general components that need to delegate, sequence or execute method calls at a time of their choosing without the need to know the owner of the method or the method parameters.		Using command objects makes it easier to construct general components that need to delegate, sequence or execute method calls at a time of their choosing without the need to know the owner of the method or the method parameters.

	[[File:2.~~gif~~]]		[[File:2.jpg]]

	<b>		<b>

Pwu6: /* Introduction */

2012-11-20T03:41:40Z

Introduction

← Older revision		Revision as of 03:41, 20 November 2012
Line 24:		Line 24:
	Using command objects makes it easier to construct general components that need to delegate, sequence or execute method calls at a time of their choosing without the need to know the owner of the method or the method parameters.		Using command objects makes it easier to construct general components that need to delegate, sequence or execute method calls at a time of their choosing without the need to know the owner of the method or the method parameters.

	[[File:~~Command_Design_Pattern_Class_Diagram~~.~~png~~]]		[[File:2.gif]]

	<b>		<b>

Pwu6: /* Command pattern on Oodesign.com */

2012-11-19T20:49:00Z

Command pattern on Oodesign.com

← Older revision		Revision as of 20:49, 19 November 2012
Line 328:		Line 328:
	'''Topics covered:'''		'''Topics covered:'''
	The reason why using Command pattern, intent of command pattern, a UML diagram to explain the adapter pattern. The application and implementation of Command patterns are mentioned. Furthermore, it presents some really great examples and specific problems where command pattern becomes a good fit to use.		The reason why using Command pattern, intent of command pattern, a UML diagram to explain the adapter pattern. The application and implementation of Command patterns are mentioned. Furthermore, it presents some really great examples and specific problems where command pattern becomes a good fit to use.
	[[File:~~OOdesign~~.jpg]]		[[File:1.jpg]]

	'''Learning:'''		'''Learning:'''

Pwu6: /* References */

2012-11-19T20:33:44Z

References

← Older revision		Revision as of 20:33, 19 November 2012
Line 395:		Line 395:
	<br>http://www.cours.polymtl.ca/inf3700/divers/nonSoftwareExample/patexamples.html		<br>http://www.cours.polymtl.ca/inf3700/divers/nonSoftwareExample/patexamples.html
	<br>http://www.cours.polymtl.ca/inf3700/divers/nonSoftwareExample/pateximg14.gif		<br>http://www.cours.polymtl.ca/inf3700/divers/nonSoftwareExample/pateximg14.gif
			<br>http://www.oodesign.com/command-pattern.html
			<br>http://coherence.oracle.com/display/INCUBATOR/Command+Pattern
			<br>https://www.informit.com/guides/content.aspx?g=java&seqNum=481
			<br>http://dotnetslackers.com/articles/designpatterns/The-Command-Pattern.aspx
			<br>http://blackwasp.co.uk/Command.aspx

Pwu6: /* Further readings */

2012-11-19T20:25:55Z

Pwu6: /* Command pattern on Informit.com */

2012-11-19T20:23:34Z

Command pattern on Informit.com

Pwu6: /* Command pattern on Informit.com */

2012-11-19T20:22:59Z

Command pattern on Informit.com

@@ Line 355: / Line 355: @@
 == [https://www.informit.com/guides/content.aspx?g=java&seqNum=481 Command pattern on Informit.com] ==
 = Further readings =
 = <b>References</b> =

← Older revision		Revision as of 20:25, 19 November 2012
Line 379:		Line 379:

	= Further readings =		= Further readings =
			*[http://blog.8thlight.com/micah-martin/2006/09/07/delegates-vs-command-pattern.html Delegates Vs Command Pattern]
			*[http://www.se.rit.edu/~se362/Misc/TypicalAreasForImprovement.html Typical Areas for Improvemen of the Design and its Documentation ( Pattern misuse )]
			*[http://www.slideshare.net/jonsimon2/command-and-adapter-pattern Command pattern and Adapter pattern]
			*[http://www.drdobbs.com/multithreaded-programming-with-the-comma/184416612 Multithreaded Programming with the Command Pattern]

	= <b>References</b> =		= <b>References</b> =
	<br>http://www.itsmedia.ca/the-command-pattern-and-restful-interfaces/		<br>http://www.itsmedia.ca/the-command-pattern-and-restful-interfaces/

← Older revision		Revision as of 20:23, 19 November 2012
Line 356:		Line 356:
	== [https://www.informit.com/guides/content.aspx?g=java&seqNum=481 Command pattern on Informit.com] ==		== [https://www.informit.com/guides/content.aspx?g=java&seqNum=481 Command pattern on Informit.com] ==

	Topics covered:		'''Topics covered:'''
	This page mainly talks about the responsibilities of different roles in Command Pattern. It gives us a simple example of using Command Pattern -- with complete code and detailed comments. It is really suitable for those who are new to this pattern.		This page mainly talks about the responsibilities of different roles in Command Pattern. It gives us a simple example of using Command Pattern -- with complete code and detailed comments. It is really suitable for those who are new to this pattern.

	~~Hot spot~~:		'''Learning:'''
	* Three roles defined in Command Pattern:		* Three roles defined in Command Pattern:
	1. Client -- is responsible for creating the command and initializing it		1. Client -- is responsible for creating the command and initializing it

	2. Invoker -- is responsible for determining when a command should be executed		2. Invoker -- is responsible for determining when a command should be executed

	3. Receiver -- is an instance of the class that receives the action of the command		3. Receiver -- is an instance of the class that receives the action of the command

	* Source code for a simple game that contains a game board, commands for moving up and down the game board, and a game that drives everything.		* Source code for a simple game that contains a game board, commands for moving up and down the game board, and a game that drives everything.
	1. GameBoard.java /the receiver ,represents a game board/		1. GameBoard.java /the receiver ,represents a game board/

	2. Command.java /the command interface/		2. Command.java /the command interface/

	3. MoveUpCommand.java /command that moves the player up one space/		3. MoveUpCommand.java /command that moves the player up one space/

	4. MoveDownCommand.java /command that moves the player up down space/		4. MoveDownCommand.java /command that moves the player up down space/

	5. Game.java /invoker class/		5. Game.java /invoker class/