[email protected] wrote: > On 23 mai 2013, at 16:31, Howard Chu <[email protected]> wrote: >> Don't do that. > > Sure, that's why I have a *bad* workaround to not update the 'objectClass' > attribute even if the original and my generated one don't match.
IMO this is not a *bad* workaround. I think it's good practice in a UI client to *not* automagically modify attribute 'objectClass' without explicit user interaction asking for modification. Ciao, Michael.
