IoC

I've recently developed an IoC engine based around the concepts of "actions", "handlers" and "managers" which key off of whatever the "KeyGenerator" is defined to be... any object. It's proving to be a highly scalable and distributable platform for a new runtime engine I'm dubbing "ActionEngine." Coupled with the ApplicationFW that has already been developed it's going to prove to be a, nearly, 100% uptime system. Imagine the ability to signal an application listen via a background thread to reload certain aspects of itself. This currently exists in most app containers (Java) but not in the .NET realm (well, somewhat) ... especially not geared towards typically business problem (e.g. monitoring, p2p, etc).

If I can actually get this done in a relatively short timespan it will most likely be deployed as the platform for our business.

If you can imagine it you can do it. The problem is it's many times difficult to explain the imagination.