My comments below.
* Support for multiple database connections in a single Django
instance.
We always had this
* Model validation inspired by Django’s form validation.
If I understand this:
http://docs.djangoproject.com/en/dev/ref/validators/#ref-validators
now django works like web2py always did. They copied us. Still their
validators cannot act as filters/reverse filters so are limited in
comparison.
* Vastly improved protection against Cross-Site Request Forgery
(CSRF).
We always had this although the implementation is very different. we
have a random _formkey in forms. Our mechanism also prevents
accidental double form submission.
* A new user “messages” framework with support for cookie- and
session-based message for both anonymous and authenticated users.
we have response.flash=DIV('message',_class='info') serves the same
purpose. Their system is obviously more complex and, I think,
unnecessarily.
* Hooks for object-level permissions, permissions for anonymous
users, and more flexible username requirements.
We do this using the role based access control (RBAC). Our system is
more flexible. RBAC is more general than other mechanisms (http://
en.wikipedia.org/wiki/Role-
based_access_control#Relation_to_Other_Models)
* Customization of e-mail sending via e-mail backends.
We are way ahead. We even support PGP emails and multiple email
backends.
* New “smart” if template tag which supports comparison operators.
We always had this since we do not restrict what Python code goes in
templates.
I am glad that while once we took some ideas from them, now they are
taking some ideas from us.
Soon we will have a Django web based IDE.
Massimo
On May 17, 5:44 pm, mikech <[email protected]> wrote:
> http://docs.djangoproject.com/en/dev/releases/1.2/
