* Phillip J. Eby <[EMAIL PROTECTED]> [020119 12:04]:
> ...
> IMHO, you don't want to share a security object between more than one 
> class, since presumably they will have different declarations and thus each 
> require their own.  So there's no reason to create a ClassSecurityInfo 
> object at the module level, anyway.

Good point. Actually, I only declared ClassSecurityInfo object at the module
level out of convenience: I thought each class (presuming there were more
than one in the module) could reference that same security object, so maybe
save a few CPU cycles in the process (plus, I saw this done in some product
I used as a learning example). But your point is well taken ... plus 
module-level security declarations have no effect at the class level.


Zope-Dev maillist  -  [EMAIL PROTECTED]
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://lists.zope.org/mailman/listinfo/zope )

Reply via email to