>Hey all
>
>DNN is very interesting. I'm looking at it from the point of view of a development framework. It provides coding standards - by way of example, a bunch of features with example code.

I'd be very careful going down that path. DNN is cool for what it does, but I don't think it would make a good choice for a general development platform. For one thing it becomes unmanageable very quickly for development once you add significant code to it. It's SLOW in development mode and starting up.

Furthermore while I think DNN provides a good model for a portal type interface, I don't think it's a good match for anything much beyond that. If you have applications that follow that path it's not that difficult to provide that functionality much more efficiently to the core application functionmality rather than strapping on a beast like DNN <g>...

One fundamental problem with DNN is that it's the master application which means right from the start you're forced into DNNs model. If you have your own framework you're SOL. IOW, it forces its model on you.

That may or may not work for you, but you should carefully test DNN with anything outside of its defined space to see whether it a) fits and b) performs properly.

+++ Rick ---