Adrian, I wonder if you could give some thoughts up on how people might migrate existing authentication (and authorisation - there's a difference ;) schemes into Django?
I have about 60+ Zope sites and their associated dev-sites using a variety of AA, from MySQL and PostgreSQL tables with 10's of thousands of users, through to LDAP and Shibboleth (the latter is only going to get more important for us as time goes on). Before getting too deeply into whether we should start using Django, I've been playing around with it on my laptop (where it scored above all but the most recent Zope3 builds in actually working! - TiPB, OS-X 10.4.3) and I do like it (particularly because I can use Zope pagetemplates as the templating language). So I'm really looking for any potential deal-stoppers before I start getting Django installed on our main server clusters... It looks like the idea of attaching a decorator to any method that needs authentication/authorisation is the way to go (and may be almost as easy as the way Zope does it), but I'd like to get the received wisdom on this subject ;) I'm not trying to start a Zope-django comparison discussion (at least on this thread!), rather I'm just trying to get as much information as I can to base my decisions on. many thanks for all thoughts Tone
