Request that the server send the client updates in order for the client to stay in sync with the server. See RFC 4533.
Note that these examples use the DefaultCookieManager which stores cookie data in memory. Most implementers will want to provider a custom implementation to persist cookie data. The interface for CookieManager looks like:
Creates a SyncReplClient to use for a content synchronization without an existing cookie. By setting the persist property to false we expect the server will send the client all content followed by a response. Which means we do not expect to block indefinitely.
Refresh and Persist
Creates a SyncReplClient to use for a content synchronization without an existing cookie. By setting the persist property to true we expect the server will continue sending us content updates until the operation is cancelled.
Functionality exists in the provider API and has been confirmed
Functionality does not exist in the provider API
Functionality exists in the provider API, but did not work in our test environment
Functionality exists in the provider API, but has not been integrated into the ldaptive provider
Ldaptive is an open source project developed and supported by
at Virginia Tech