[PATCH] s4-drs: Delete RODC filtered attributes from objects

[Fernando J V da Silva]

Hi guys!

2010/3/12 Fernando J V da Silva <fernandojvsilva at yahoo.com.br>:
>> When a DC is a RODC, then when it replicates from another DC, it gets
>> a subset of the attributes. So there is no need for it to delete
>> attributes. The reason it gets a subset is that a RODC is not trusted
>> to hold all attributes, so they will never be sent by the other DC.
>
> Actually, in this first patch, I was trying to handle the following
> situation (not so usual, but that may happen and is related to the
> manually set of a RODC filtered attribute on a DC that I was studying
> ...): Firstly, suppose you set an attributeSchema (any attribute you
> want ...) to be RODC filtered (like in
> http://technet.microsoft.com/en-us/library/cc772331(WS.10).aspx), but
> also suppose that you already have some objects whose contain values
> for that attribute and those objects are already replicated to your
> RODC; After that, the attributeSchema that you've changed is
> replicated to your RODC (at least that was what happened during my
> W2K8<->W2K8 tests ... (it should not  happen?) ); When it happens,
> such attribute's value vanish from those objects whose had it and were
> stored in the RODC.
>


BTW, according to the comments here, now I think that what this patch
does, could possibly be necessary (despite such unusual situation
...), but the code may not be in the right place (in a RODC, it
shouldn't reach the modules when modifying an object after receiving
an GetNCChanges reply, should it?).

Anyway, it seems to me that what this patch does, should happen after
receiving an GetNCChanges reply containing an attributeSchema object
which is RODC filtered...

Am I saying something reasonable?


Cheers,

-- 
Fernando J V da Silva
M Sc Computer Science Student
Institute of Computing, State University of Campinas
+55 15 8801-2165