- TrIpLeZoNe -

This is just my rambling, so ignore if you're not interested.

There has always been people creating frameworks for others to use, and patterns being advocated to be widely used and should be used. But what about creating a framework of patterns? Frameworks in a sense are a set of APIs that enable you to use and aid you in creating an application in a particular domain, or basically to aid you in any part of your application development. Patterns are ways of solving a problem that works and always works.

I'm not good at explaining, but I hope you understand. Writing a "Framework of Patterns" basically means to write a reuseable framework with all the common types of frameworks that you can inherit and extend from, or tagging a pattern attribute to your class which allows you to quickly use and create a pattern for your own needs. Sounds cool? Yes, it is, and with generics you should be able to create something like this.

Ok, now with 3 major ideas at hand, I guess I'll be requested people to help me out.

1) New Client-Side programming language

2) .NET Enterprise Platform Specification

3) Framework of Patterns

I hope I can find people in my university to help me embark these 3 ideas. :)

Further thinking about Paladin's abstraction of Auditing out of the data layer, I've been thinking about Policy-based programming, where you mix and match different policies that you need using templates/generics, but then again, Auditing would be part of the AOP structure, where technically it should be an attribute, just like logging. But performance-wise, reflection is pretty slow. So there's still the drawbacks here. How does one actually make AOP fast? I'm wondering.

For those interested in anything I've just been rambling about, please leave me a comment or an email and we can discuss further.