Comments inline... On 1/31/11 2:59 PM, Alex Karasulu wrote: >
(3) Regardless of what is stored in the value, no application
can just use > it as is without some kind of component to
decode, parse, or interpret this > binary data. It's useless to
API users otherwise. It's opaque according to > LDAP, but there
has to be some meaning to make use of this content, and that >
always requires some code to convert that binary data into
usable > information. A useful representation to an API user is
a parameterized > representation making the opaque structure
transparent. I can imagine a use case where someone has 2 LDAP
servers, he get some response from server A, with a control he
does not know anything about, and has to send the value stored
into the control without having to decode it, to send it as a
control in a request sent to server B. Ok, a bit far fetched,
but this *can* be a use case. But let's think about the
replication control now. It works in a way we get a cooie from
the server we are contacting, and w