At 01:12 PM 1/18/02 +0100, Stefan Bund wrote:
Phillip J. Eby [EMAIL PROTECTED] writes:
Method rebinding is done only when an item is retrieved from the aq_self
side, and only if im_self points to aq_self. If these conditions are met,
a new binding is created which points to the
Just a word to thank you for your reply.
But incidently, wouldn't it be a good idea for Globals.InitializeClass()
to throw an error
or a warning of some kind for hanging 'security.stuff()' declarations,
declarations which do not have a related ClassSecurityInfo object AT THE
CLASS LEVEL? To the
vio wrote:
Just a word to thank you for your reply.
But incidently, wouldn't it be a good idea for Globals.InitializeClass()
to throw an error
or a warning of some kind for hanging 'security.stuff()' declarations,
declarations which do not have a related ClassSecurityInfo object AT THE
* vio [EMAIL PROTECTED] [020119 09:56]:
vio wrote:
Just a word to thank you for your reply.
But incidently, wouldn't it be a good idea for Globals.InitializeClass()
to throw an error
or a warning of some kind for hanging 'security.stuff()' declarations,
declarations which do not have
vio wrote:
deletia
So Globals.InitializeClass(your_class) finds the declaration
'security.declareSomething()' inside a class, but 'security' being
a reference to a ClassSecurityInfo object AT THE MODULE LEVEL somehow has
no effect at the class level (while I wrongly thought that by
You are right, I struggled a lot to understand Zope's declarative security
model. And I am still learning, so practice makes better. I didn't read
Globals.InitializeClass() source, and I wrote my following comments out of the
blue. Developping an error-correcting system might still be a little
At 10:43 AM 1/19/02 -0500, vio wrote:
* vio [EMAIL PROTECTED] [020119 09:56]:
So Globals.InitializeClass(your_class) finds the declaration
'security.declareSomething()' inside a class, but 'security' being
a reference to a ClassSecurityInfo object AT THE MODULE LEVEL somehow has
no effect at the
* 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
