A good pattern replicates it very quickly. The pipeline pattern (or sometimes intercepting filter pattern) makes into the Enterprise Library 3.0, particularly with the introduction of Policy Injection Application Block.
Previous notable examples of pipeline patterns in Microsoft's technologies are ASP.NET's HttpModule, WSE's Input/Output Filter and WCF's pre/post-call processing Channels.
In EL 3.0, Policy Injection AB is just meant to have a pipeline for "cross-cutting concerns" of functional method, such as validation, logging, authorization, performance instrumenting, exception handling. Policy is one of such cross-cutting concern that is enfored upon a policy-enabled method. Of course, such policy is configuration enabled and declarative thus "injected" by the framework during the runtime (hence the name). Implementation of all such cross-cutting concerns could be delegated to the existing Application Blocks of the EL - what a nice wiring after all!
EL 3.0
http://www.microsoft.com/downloads/details.aspx?familyid=62EF5F79-DAF2-43AF-9897-D926F03B9E60&displaylang=en
Posted
Apr 17 2007, 01:02 AM
by
blackinkbottle