On 14/1/06 10:25, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > Hm, the way I read RFC 2252 4.3.2 it means suggested maximum (<quote>A > suggested minimum *upper* bound</quote>). The client is advised to stay > below this number of bytes/chars but the server should allow for more.
Yes, it is a sort of minimum maximum. :-)) > So it seems the server can safely ignore this ;-) You might still want to impose some sort of limit to avoid DoS problems. > Given the fact that an attribute can have multiple supertypes (its an > array), is there a chance that this will result in conflicting matching > rules ? (e.g. caseIgnore and caseSensitive). Or is it up to the server > to check this when loading the schema ? RFC 2252 and X.501 say that attributes can only have a single supertype. I'm not sure why our Schema class allows for multiple - maybe to cope with multiple names for a single supertype? There's no reason why couldn't define a subtype with different matching rules - if you don't define a matching rule then you should inherit the supertype's matching rule (which might inherit from the supertype's supertype etc etc). Cheers, Chris
