You could be right; I own the GoF book but didn't have it open when I was writing that code and documentation. Chain of Responsibility is closer.
On Sat, Nov 28, 2009 at 7:57 AM, Thiago H. de Paula Figueiredo <[email protected]> wrote: > Hi! > > Just a documentation nitpick: Tapestry's documentation talks about the Chain > of Command design pattern. The GoF book > (http://en.wikipedia.org/wiki/Design_Patterns:_Elements_of_Reusable_Object-Oriented_Software), > the most used reference about design patterns doesn't have one named Chain > of Command pattern: it has the Chain of Responsibility pattern, that AFAIK > is what the Tapestry documentation calls Chain of Command, and there's a > Command pattern. > > Google show us 17500 pages for "Chain of Command design pattern", while > 89000 "Chain of Resposibility design pattern". > > I think the documentation should use the most used name of this design > pattern. Do you agree? If yes, I think we should change the documentation > (including source comments), as theses pattern (Chain of Responsibility and > Command) are used a lot in Tapestry, and Chain of Command can be confused > with Command. > > -- > Thiago H. de Paula Figueiredo > Independent Java, Apache Tapestry 5 and Hibernate consultant, developer, and > instructor > Owner, software architect and developer, Ars Machina Tecnologia da > Informação Ltda. > http://www.arsmachina.com.br > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- Howard M. Lewis Ship Creator of Apache Tapestry The source for Tapestry training, mentoring and support. Contact me to learn how I can get you up and productive in Tapestry fast! (971) 678-5210 http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
