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]
