When considering the phylogenic properties (sorry, I couldn't help myself) of a given pattern I almost always think of the GoF patterns first. You can choose to see a "new" pattern as entirely new or you can instead see the *patterns within the patterns*. Many of the more domain-specific patterns are simply derivations of more fundamental patterns; knowing these fundamental patterns will certainly expedite the knowledge assimilation time.
An example might be MVC. Over the years I've seen so many different implementations claiming to be MVC that I have little regard for what it actually means to be "true" MVC; indeed, many have attributed new names for these "new" patterns (e.g. Model-View-Presenter), but it's much easier to consider it when knowing its roots. Kind regards, Chad On Wed, 30 Mar 2005 07:19:10 -0500, Bill Bassler <[EMAIL PROTECTED]> wrote: > I think I remember seeing this pattern when I went through the Microsoft > Enterprise Solutions patterns whitepaper. To me anyway, this pattern really > seems to fit requirements I have. BTW. Another implementation I see of this > pattern is in Web Services Extentions soap message filtering. > > One question. What is the origin of this pattern? It's not a GoF pattern. > Are the GoF patterns considered "low level" patterns. Is the interception > filter more at the level of a Martin Fowler "Enterprise Integration > Pattern" or enterprise solution pattern? In other words, how do I know that > I'm considering every pattern available against a given set of requirements. > > =================================== > This list is hosted by DevelopMentor(r) http://www.develop.com > > View archives and manage your subscription(s) at http://discuss.develop.com > =================================== This list is hosted by DevelopMentor� http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
