Re: [Zope-dev] LDAPRoleTwiddler / BasicUserFolder

2002-10-17 Thread Jens Vagelpohl
why is that code no longer referring to the real userfolder anymore? it should not make calls to authorize/identify/authorize on self but on the LDAPUserFolder it is using as the user source. jens On Thursday, Oct 17, 2002, at 03:39 US/Eastern, Dirk Datzert wrote: Hi all, I try to solve

Re: [Zope-dev] How to override __getattr__ and not break acquisition

2002-10-17 Thread Steve Alexander
I perhaps should have clarified that I need to be able to specify the name of the attributes or methods at run time, so ComputedAttribute unfortunately won't do the trick as you have to define each attribute/method you require in the class definition. ie. I need something like : def

Re: [Zope-dev] LDAPRoleTwiddler / BasicUserFolder

2002-10-17 Thread Dirk Datzert
Hi Jens, why is that code no longer referring to the real userfolder anymore? it should not make calls to authorize/identify/authorize on self but on the LDAPUserFolder it is using as the user source. self.identify() should be the same as if getLUF().identify() since LDAPUserFolder and

Re: [Zope-dev] LDAPRoleTwiddler / BasicUserFolder

2002-10-17 Thread Jens Vagelpohl
being explicit is almost always better. you are relying on internal magic and it's not apparent from looking at the code you wrote. the validate implementation in the LDAPRoleExtender is the most correct one. shane worked on it for a while to make sure it does the most correct thing possible,

Re: [Zope-dev] How to override __getattr__ and not break acquisition

2002-10-17 Thread John Barratt
Casey Duncan wrote: __getattr__ hooks are evil, only to be used as a last resort. Are you So I've found, and heard! It didn't stop me from tyring, and I still don't see why they should be so hard so work with, difficult perhaps, but I wouldn't have though you needed to pull the seemingly

Re: [Zope-dev] How to override __getattr__ and not break acquisition

2002-10-17 Thread John Barratt
There is no default or normal __getattr__. __getattr__ is defined only when you need abnormal ways of getting an attribute. Do you mean it only gets defined when standard (instance class based) searching methods fail? If I try a similar thing to this, I always end up getting the 'old' one

Re: [Zope-dev] LDAPRoleTwiddler / BasicUserFolder

2002-10-17 Thread Shane Hathaway
Jens Vagelpohl wrote: being explicit is almost always better. you are relying on internal magic and it's not apparent from looking at the code you wrote. the validate implementation in the LDAPRoleExtender is the most correct one. shane worked on it for a while to make sure it does the most

Re: [Zope-dev] How to override __getattr__ and not break acquisition

2002-10-17 Thread Lennart Regebro
From: John Barratt [EMAIL PROTECTED] Do you mean it only gets [called] when standard (instance class based) searching methods fail? Yes. At least, this is what the documentation sais, and it seems to be true as far as I can see. Object Manager doesn't specifically, but Implicit does, you can

Re: [Zope-dev] LDAPRoleTwiddler / BasicUserFolder

2002-10-17 Thread Dirk Datzert
Hi Shane, thanks for answering. Maybe I'm think too complicated, Your opinion ? The idea behind LDAPRoleExtender is to give the user global roles if the I don't know anything about LDAPRoleTwiddler. But I would recommend you install the VerboseSecurity product, which will tell you a

Re: [Zope-dev] LDAPRoleTwiddler / BasicUserFolder

2002-10-17 Thread Dirk Datzert
if I access /dir2/index_html comes the user object from LRT2 ? what if I access in /dir2/index_html aq_parent.dir1.index_html. Will the AUTHENTICATED_USER change ? will the user object come from LRT2 ? No, it will not. Only one user ever applies to a request. And that exactly what

Re: [Zope-dev] Proposal: Improving ZSQL Methods

2002-10-17 Thread Adrian Hungate
Hmm... (a) Is a great idea (b) How would this work in practice? Adrian... -- Adrian Hungate EMail: [EMAIL PROTECTED] Web: http://www.haqa.co.uk - Original Message - From: Andy McKay [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, October 17, 2002 11:07 PM Subject: [Zope-dev]

Re: [Zope-dev] Proposal: Improving ZSQL Methods

2002-10-17 Thread Andy McKay
(b) How would this work in practice? Make a RAM Cache Manager, and then assign the ZSQL Method to cache in that cache manager, just like you would any other object. The results are then cached according to the database connection and the query in the RAM Cache Manager. It means we have a much

[Zope-dev] Re: Reports of CallProfiler not working with Zope 2.5.x were greatly exagerated :-) (was Re: CallProfiler?)

2002-10-17 Thread Richard Jones
On Fri, 18 Oct 2002 6:07 am, Leonardo Rochael Almeida wrote: CallProfiler wasn't profiling ZPTs because they've been renamed/moved from Products.PageTemplates.PageTemplates.PageTemplates to Products.PageTemplates.ZopePageTemplate.ZopePageTemplate. Here's a patch to make it work again. I'll