June 24, 2005
Design Patterns
Random Thoughts on the Provider Pattern
I found an entry in Wikipedia on Aspect Oriented Programming (and no, I wasn't randomly reading Wikipedia, I got there from somewhere else... honestly).
I know nothing about AOP, but from this quick overview in Wikipedia it occurred to me that the Provider Pattern is a model for handling crosscutting concerns in object oriented applications. Sounds fancy doesn't it, but it's not. Crosscutting concerns are simply the things that appear everywhere in applications -- things like logging and transactions. The crosscutting concerns get tangled with and obfuscate the core business logic, a.k.a. the business logic concerns. Yeah, everything is a concern in AOP...
Posted by Adam Boddington at 11:48 AM | Comments (0)
June 06, 2005
.NET | Design Patterns | SevenCamels.Framework.Configuration
Plugin the Provider Pattern
I finally took a look at the Provider Pattern outlined by Rob Howard in MSDN's "Nothin' But ASP.NET" column. There's a Part II as well which comes with a nifty little code example. It's very similar to some work that I've already done with plugins defined in configuration files, so I thought I would abstract my work out a bit more and see if I could get it to support the Provider Pattern as well. Extending it to cater for providers was pretty simple with a little refactoring, but before I start talking about the code, lets take a look at what the Provider Pattern actually is.
Posted by Adam Boddington at 01:20 PM | Comments (0)

