directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Karasulu (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DIRSERVER-939) Implement RFC 4529
Date Tue, 22 May 2007 23:04:16 GMT

    [ https://issues.apache.org/jira/browse/DIRSERVER-939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12498052
] 

Alex Karasulu commented on DIRSERVER-939:
-----------------------------------------

This is an extremely interesting feature for LDAP.  I say this because as you know entries
can have any number of AUXILIARY objectClasses and these different objectClasses are a different
aspect or view of the entry.  By requesting a specific set of attributes based on the objectClass
client code for marshalling objects for a specific interface is simplified.  I can see several
use cases for this.  However I do think this is a nice to have feature rather than a critical
one.

+1 to add it and adding it should not at all be that difficult considering how well isolated
the code is for returning various attributes.  I suspect there is a request control in here
that is involved with the search request to modify the returned set of attributes.  

> Implement RFC 4529
> ------------------
>
>                 Key: DIRSERVER-939
>                 URL: https://issues.apache.org/jira/browse/DIRSERVER-939
>             Project: Directory ApacheDS
>          Issue Type: New Feature
>    Affects Versions: 1.5.0
>            Reporter: Emmanuel Lecharny
>            Priority: Minor
>             Fix For: 1.5.2
>
>
> It would be interesting to implement RFC 4529, which says that if we add an objectClass
into the list of returned attributes, then all the objectClass attributes are to be returned.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message