Lines Matching refs:content
123 request directory content matching a complex set of assertions and to
124 request that the server return this content, subject to access
128 synchronized copies of directory content. This document introduces a
129 new mechanism specifically designed to meet the content
140 Over the years, a number of content synchronization approaches have
152 content and/or meta information;
160 content when possible and, when not, notification that a full reload
195 and the number of unchanged entries in the content. The operation is
196 designed to avoid full content exchanges, even when the history
199 of out-of-content history information, as its size is not bounded by
200 the content and it is not always feasible to transmit such history
209 eventually-convergent content synchronization. Upon completion of
211 construct a synchronized client copy of the content has been provided
212 to the client or the client has been notified that a complete content
215 copy is an accurate reflection of the content held by the server.
242 coherent content cache.
257 the content upon change instead of change deltas, this protocol is
275 restrictions) the content matching the search criteria (baseObject,
288 change over time, an entry's UUID is stable. The initial content is
295 as it would with a normal search operation, determines which content
297 However, using the syncCookie as an indicator of what content the
301 to the content are sent.
305 entries deleted from the content: the present and the delete phases.
322 content and the number of such entries is less than or equal to the
325 each entry that is no longer in the content, instead of returning an
334 content are contained in the syncUUIDs set. An optional cookie can
343 be included in the syncIdSet to represent the state of the content
353 Sync Operation, but whose content is provided by the previous Sync
355 deleted from the client content. They had been either deleted,
356 moved, or otherwise scoped-out from the content.
361 identified as having been deleted from the content.
370 updates of changed entries in the content.
374 refresh content is determined. Instead of sending a SearchResultDone
383 server. For entries to be added to the returned content, the server
385 indicating state add. For entries to be deleted from the content,
388 modified in the return content, the server sends a SearchResultEntry
400 attributes belonging to the content are sent.
403 where the entry is renamed into the content, a delete state change
404 where the entry is renamed out of the content, and a modify state
405 change where the entry remains in the content. Also note that a
407 modify state change to the content.
410 the content.
603 cookie indicates a request for initial content, while the presence of
605 for a content update. Synchronization Sessions are discussed in
629 The client MUST specify the same content-controlling parameters (see
636 content as if no cookie had been provided or return an empty content
638 between the return of the initial content and the return of the empty
639 content with the e-syncRefreshRequired result code MAY be based on
643 initial content.
652 The content to be provided is determined by parameters of the Search
654 same content parameters SHOULD be used in each Sync request of a
655 session. If different content is requested and the server is
657 the initial content as if no cookie had been provided or return an
658 empty content with the e-syncRefreshRequired LDAP result code. The
659 decision between the return of the initial content and the return of
660 the empty content with the e-syncRefreshRequired result code MAY be
663 The content may not necessarily include all entries or references
687 separate content synchronization session.
692 initial content. A Sync request with mode refreshOnly and with a
693 cookie representing a synchronization state is a poll for content
698 Upon receipt of the request, the server provides the initial content
714 result code on the initial content poll if it is safe to do so when
717 the initial content poll.
725 Upon receipt of the request, the server provides the content refresh
741 convergence of the client's copy of the content to the server's
744 b) treat the request as an initial content request (e.g., ignore
758 content or been changed since the previous Sync Operation indicated
777 that are no longer in the content.
792 syncIdSet may contain a cookie to represent the state of the content
795 In the delete phase, for each entry no longer in the content, the
800 reference no longer in the content, a SearchResultReference
809 content since the last Sync Operation. syncUUIDs may be empty. The
811 state of the content after performing the synchronization of the
824 the state of the content after completing the Sync Operation. The
831 SHOULD contain a cookie representing the state of the content after
836 content by supplying reloadHint of TRUE or to receive a e-
859 A Sync request with mode refreshAndPersist asks for initial content
860 or content update (during the refresh stage) followed by change
865 The content refresh is provided as described in Section 3.3, except
866 that the successful completion of content refresh is indicated by
870 Info Message to represent the state of the content after finishing
878 changes to the content. DIT updates may cause entries and references
879 to be added to the content, deleted from the content, or modified
880 within the content. DIT updates may also cause references to be
881 added, deleted, or modified within the content.
883 Where DIT updates cause an entry to be added to the content, the
885 as it appears in the content. The message SHALL include a Sync State
889 Where DIT updates cause a reference to be added to the content, the
891 reference in the content. The message SHALL include a Sync State
903 Where DIT updates cause an entry to be modified within the content,
905 entry as it appears in the content. The message SHALL include a Sync
910 content, the server provides a SearchResultReference Message that
911 represents the reference in the content. The message SHALL include a
915 Where DIT updates cause an entry to be deleted from the content, the
920 Where DIT updates cause a reference to be deleted from the content,
930 content. The Sync Info Message of syncIdSet may contain a cookie to
931 represent the state of the content after performing the
943 content-controlling parameters in each Search Request of the session.
944 All fields of the SearchRequest Message are considered content-
1017 content, the server may provide an empty DN if the server does not
1071 The decision between the return of the initial content and the return
1078 copy of the content. If no cookie is provided, a full refresh is
1093 refresh the client content does not exceed the number of entries
1094 presently in the content. While there is no requirement for servers
1097 copy are no longer present in the content and the number of such
1118 determine if no changes were made in the context since the content
1143 changes do not cause content synchronization changes to be
1202 moving could cause the entry to be added or deleted from the content,
1254 Modification of a collective attribute generally affects the content
1275 Where it is impractical or infeasible to generate content changes
1278 initial content request (e.g., ignore the cookie or the
1313 whether an entry or subentry appears in the content.
1319 servers may also support content synchronization requests. This
1325 of being used to obtain particular directory content from, a client
1327 continuing a content synchronization session. As stated in Section
1337 logical server SHOULD be equally capable of continuing a content
1352 what content was provided to the client by another server, especially
1359 In order to maintain a synchronized copy of the content, a client is
1360 to delete information from its copy of the content as described
1362 disclosed to it by the server separate from its copy of the content
1365 information for content the client is not authorized to have
1372 sequence of update operations that caused content change.
1375 content, including malformed cookies or valid cookies used with
1614 to be serialized, one cannot assume that the returned content
1616 less than or equal to the greatest entry CSN in the content. The
1617 content incorporates all the relevant changes whose change sequence
1619 processing. The content may also incorporate any subset of the
1622 after search processing. The content does not incorporate any of the
1638 simply generate "update" messages for all entries in the content
1640 "present" messages for all other entries in the content. However, if
1646 information, such as access controls, that affect content
1649 be updated whenever meta information affecting content determination
1652 initial request for content.