>> Do you think this is design overkill?
>> i.e. document clearly instead.
>
>I guess I'd vote for the documentation choice, rather than adding
>extra interfaces, since those aren't completely free.
>
Ok, i will strip 'em down.
>> In relation to filters and searches:
>> I notice that URL search has been removed from
>> the nsILDAPOperation interface. I think
>> i remember reading why some time ago but
>> its lost on me now....
>
>Because it was just a wrapper for ldap_url_search(), which claims to
>be async, but under the covers it's really not. See
><http://bugzilla.mozilla.org/show_bug.cgi?id=44017> for details.
>
Thanks. I have changed our LDAP code to use
searchExt and use the LDAP URL just
like the js LDAP RDF data source.
>> I think as long as the nsILDAPUrl is fully
>> featured it does not matter because the
>> appropriate parameters for the searchExt
>> method could be obtained from this interface.
>
>Right, this was exactly the thinking here.
>
Yep.
It would be nice if the existing
nsILDAPOperation.seatchExt method included the
returned attributes parameter as support in the
nsILDAPURL interface :-)
Paul.
| ? + ? = To question
----------------\
Paul Sandoz
x19219
+353-1-8199219
