[Date Prev][Date Next]
Re: Undefined attribute types and proxy (Was: (ITS#3951) send_search_entry() issue when determining whether an attribute is to be returned or not)
At 01:19 AM 8/19/2005, Pierangelo Masarati wrote:
>Pierangelo Masarati wrote:
>>Possible solution: we could define a "proxy-undefined" attribute type that is not dsaOperation, but noUserMod, and derive from that the undefined attributes resulting from proxying.
>The cleanest solution is to import the schema from the remote server.
I don't know if I'd call this a clean solution. Dealing with
incomplete schema descriptions, unsupported/unknown matching rules
and the like would be quite messy and dirty.
I rather just treat unknown stuff as some pass-through blob
(blob here imply that we would never do any matching against
the values (which may have impact in ACLs and elsewhere)).
>A mechanism to sync it runtime would be best (e.g. persistent search on subschemaSubentry, if available, or periodically scheduled checks would be an option). Unfortunately some DSA implementations are quite forgiving, if not deceiving, in defining schema... this would require some repairing policy.
> SysNet - via Dossi,8 27100 Pavia Tel: +390382573859 Fax: +390382476497