[Date Prev][Date Next]
Re: commit: ldap/servers/slapd/overlays pcache.c
Howard Chu wrote:
> Michael Ströder wrote:
>> Howard Chu wrote:
>>> firstname.lastname@example.org wrote:
>>>>> hyc@OpenLDAP.org wrote:
>>>>> Detecting renames will be trickier since the cache typically won't
>>>>> have any entryUUIDs. I think we'll simply have to treat it as a
>>>>> Delete / Add...
>>>> ... which makes sense for a cache, all in all.
>>>> Or, as implementing this feature seems to move towards on-demand sync
>>>> replication, we could always include entryUUID and entryCSN in the
>>>> requested attributes, e.g. by implicitly adding them to the attrsets.
>>> Yes, but that's only viable if the target server supports entryUUID and
>>> entryCSN. There are plenty of pcache use cases where this will not be
>> Other LDAP servers have similar attributes.
>> entryUUID: GUID on eDirectory, objectGUID on MS AD and ADAM.
>> Similar for entryCSN. (Can look up these if needed.)
>> How about making this configurable?
> pcache has been working fine without explicit support of these so far,
> and they're not critical to the current work.
I agree it's not critical.
> I'm not opposed to someone
> adding these later, but I don't have time for them right now.
It was just a suggestion.