-----BEGIN PGP SIGNED MESSAGE-----
Shane Hathaway wrote:
> Philipp von Weitershausen wrote:
>> Shane Hathaway wrote:
>>> However, I'm wondering what browser:page does to make something
>>> publishable, that browser:view doesn't do.
>> It creates a new class with an extra mix-in class that has a
>> browserDefault method which in turn points to the template, method or
>> __call__ attribute.
> If you don't mind explaining, I'd like to understand why this design was
> chosen. Why does it create a new class instead of creating an instance
> of a class? It seems like it's using advanced Python (class generation)
> where ordinary Python (a class instance) will do just as well.
> If I'm not missing something important, I may try to rewrite that code.
I *think* that the design predated the ability of the security machinery
to use an instance-specific attriubute for the checker, and so the only
feasible way to get the configuration-specified security settings was to
generate code. Either that, or the implementor didn't understand how
the checker machinery worked, and just "made it work."
'pushpage' has a view directive which uses instances, rather than
Tres Seaver +1 202-558-7113 [EMAIL PROTECTED]
Palladion Software "Excellence by Design" http://palladion.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v220.127.116.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----
Zope3-dev mailing list