Lines Matching refs:clients
147 The LCUP protocol is intended to allow LDAP clients to synchronize
152 - Mobile clients that maintain a local read-only copy of the
189 particular group of clients (e.g., on-line clients or off-line
190 clients), none satisfies the requirements of all clients in the
196 information specific to individual clients. The server may need to
198 deleted entries, and moved/renamed entries. The clients are
203 retrieve the changes. LCUP design requires clients to initiate the
290 to LCUP clients. For cookie schemes that expose their value, the
630 Some clients may have unreliable connections, for example, a wireless
631 device or a WAN connection. These clients may want to insure that
634 redundant entries. These clients should set the sendCookieInterval
636 Some clients may have a limited bandwidth connection, and may not
639 successful completion). These clients should set the
659 value that matches the clients search filter), or by some meta-
669 (e.g., adding an attribute value that matches the clients search
1016 be used as a security mechanism to disconnect clients that are
1169 the client use an exponential backoff strategy, but different clients
1190 provide indexing or other mechanisms to allow clients to search for
1241 Contexts in the search scope first, in order to allow the clients to
1270 sending notifications to ensure that clients' needs for timeliness of
1358 clients. The protocol provides the means to stop malicious clients
1361 clients. In addition, the servers SHOULD provide the means to limit
1466 useful by clients that are currently not included in the protocol
1520 been added or just modified. It is easy for clients to determine if
1546 Some earlier synchronization protocols allowed clients to control the
1548 intended to allow clients with limited resources to process
1554 clients that can deal with the limitations of the LDAP protocol will
1562 delete operations. This ordering helps clients to maintain a