[Zope-dev] I want Zope 2.9 to use Zope 3's security architecture.

[Richard Jones]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Thu, 7 Apr 2005 02:49 am, Jim Fulton wrote:
> Paul Winkler wrote:
> > i.e. will I still write:
> >
> >     security.declareProtected(SomePermission, 'foo')
> >     def foo(self):
> >         ...
>
> That will work, and I don't see a need to deprecate it.
> Eventually, though, I expect products to migrate to
> ZCML-based security declarations.

Is this a general trend for Zope 2? I'd rather see Zope 2 kinda avoid ZCML if 
possible. It's just one of those personal preference things, I suppose, but I 
know I'm not the only one who isn't that enamored of the ZCML approach. I 
actually like having the declarations all in the python code like it is in 
Zope 2.

I'd like to see the declarative style that Zope 2 move to using decorators. I 
was sitting in a presentation at PyCon talking about MetaClasses, and I 
finally *got* them. I realised that the security declarations in Zope 2 are a 
perfect fit for metaclasses and decorators. If only I had the time to 
actually implement this dream ;)

Note that this all comes from the perspective of someone whose only exposure 
to Zope 3 has been through two sprints. I've not actually tried to develop 
any sort of application using it. My day job is very firmly fixed in Zope 2, 
and isn't likely to change for a long time. So I'm definitely speaking from 
ignorance of real-world application development in Zope 3.


     Richard
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFCVIIirGisBEHG6TARAowSAKCGSgaIkZeLJfg1NFlnzKdhOZDa3QCePu30
f5MPM1sUwbBEVykehbyNH7o=
=v736
-----END PGP SIGNATURE-----