I haven’t done much reading about the “official” [patterns], like in the book ["Design Patterns"], but I’ve always understood patterns to be a concept more than something set in stone. I think someone once told me that design patterns are descriptions of things you already do, or maybe partially do, when you write software. They’re more descriptive than prescriptive you could say.
Anyway, in a few of the web-based applications I’ve written I’ve used this pattern that I’ve started calling the Context pattern. It’s probably more of a model than a pattern, as it’s comprised of a few components. It’s not quite fully fleshed out yet, but here are the basics of it (in fact I think I’ve heard of a pattern that someone called the delegator pattern, and it’s probably a lot like this, I should look it up):
: http://en.wikipedia.org/wiki/Design_Patterns “Design Patterns Wikipedia entry”
: http://en.wikipedia.org/w/index.php?title=Special:Booksources&isbn=0201633612 “Design Patterns ISBN info from Wikipedia”