[
https://issues.apache.org/jira/browse/DIRAPI-189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13972805#comment-13972805
]
Emmanuel Lecharny commented on DIRAPI-189:
------------------------------------------
The problem is that the API is supposed to be used both side (client and
server). How should we know which side we are on ?
If we are on the client side, we should have a factory that encode the
AdDirSync control and decode the AdDirSyncResponse control
If we are on the server side, this is the opposite...
OTOH, there is no reason for using the server side control, ever... ADS will
*never* implement the Ad DIRSYNC protocol...
> Support DirSync control
> -----------------------
>
> Key: DIRAPI-189
> URL: https://issues.apache.org/jira/browse/DIRAPI-189
> Project: Directory Client API
> Issue Type: Wish
> Affects Versions: 1.0.0-M21
> Reporter: Robert Hou
> Fix For: 1.0.0-M22
>
>
> I originally wanted to impletent DirSync Control using Apache API. After I
> looked into existing Controls under
> org.apache.directory.api.ldap.model.message.controls. I think it's difficult
> to me. I can't understand the decoding and encoding of controls specification
> of Apache. So I want Apache team give implementation for this control.
> Details for this control, please refer to
> http://msdn.microsoft.com/en-us/library/ms677626(v=vs.85).aspx.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
