is (1) the 'middleware' ? On 11/14/05, Simon Willison <[EMAIL PROTECTED]> wrote: > > Hi all, > > I'm presenting Django to a crowd of 200+ people on Thursday as part > of the London Web Developer Frameworks evening ( http:// > blog.unixdaemon.net/cgi-bin/blosxom.pl/2005/10/27 ). I'm putting the > slides together now and I want to do one detailing the various high- > level components of Django. I've identified these as: > > 1. The core thingy that hooks in to the web server, maps URLs to > views, handles errors and middleware and configuration > 2. The object-relational mapper > 3. The template system > 4. The admin backend application > > It struck me that it would be really useful to have names for these > components - especially number 1. We could call it "the controller" > but I don't think that fits the definition of MVC very well. > > If you look at Rails they have great names for their different bits - > ActionController, ActiveRecord, ActionView etc. It would be handy if > we had the same thing - not just for presentations but also for > easier discussion on the lists / in changesets etc. > > Cheers, > > Simon >
-- [EMAIL PROTECTED] -- ++61-3-9877-0909 If everything seems under control, you're not going fast enough. - Mario Andretti
