[ZPatterns] a LDAP-AttributeProvider again

[steve]

Hi Ulrich,

	Umm.. are you creating a subclass of AttributeProvider in Python? Or
are you using SkinScript to create an attribute provider e.g.,

WITH LDAPQuery(self.id) COMPUTE attrib1, attrib2, attrib3

???

-steve

Ulrich Eck wrote:
> 
> hi steve,
> 
> >
> > Have you looked at the SkinScript for triggers?
> >
> > WHEN OBJECT CREATED, CHANGED, DELETED CALL ..
> >
> > also there is the OTHERWISE LET .. clause of an attribute provider that
> > you could use to return something intelligent if there is no such object.
> >
> 
> I'm not shure about the default behavior of an attribute-provider ..
> 
> I have an Interface that allows to:
> _AttributeFor()
> _SetAttributeFor()
> _DelAttributeFor()
> 
> so I have no possibilty to tell the attribute-provider to create a new
> object
> (this wouldn't be a problem as i just create a new one with its id and store
> its attributes when there is no object with this id) but when an object
> is deleted .. I don't now how to handle this situation .. this is what a
> rack
> basically does not an attribute-provider .. I think this is related to the
> "remove orphan slots" button in storage .. that would mean, that I
> need a method that cleans up my LDAP-Directory from time to time
> and deletes all objects that have no more attributes .. Is this the right
> way??
> 
> thanks for your answer
> 
> Ulrich Eck