Lines Matching refs:operations

32    of update operations within a pair of LDAP extended operations to
33    notify the server that the update operations in the framed set are
34    related in such a way that the ordering of all operations can be
36    the client.  Update operations can be grouped within a single
127    standard LDAP [RFC2251] update operations.  However, this protocol
129    update operations asynchronously and still allow the server to
130    maintain proper ordering of the operations.  It also allows the
132    large set of update operations and then to change its processing
133    strategy to more efficiently process the operations.
144    (acting as a client) that supplies a set of update operations to a
148    processes) the sequenced set of update operations sent to it by a
153    LBURP frames a set of update operations within a pair of LDAP
154    extended operations that mark the beginning and end of the update
155    set.  These updates are sent via LDAP extended operations, each
157    operations to be performed by the consumer.  Except for the fact that
159    update operations in each subset are encoded as LDAP update
160    operations and use the LDAP Abstract Syntax Notation One (ASN.1)
197    containing an ordered list of LDAP update operations to be applied to
202    sequence number by applying the LDAP update operations in its
207    When the consumer has processed the update operations from an
209    indicating the success or failure of the update operations contained
276                      of one or more LDAP update operations (see section
289                LDAP update operations contained within each
294                consumer completes processing the update operations
315    update operations from the supplier to the consumer.  These three
402    send no more than that number of update operations per
405    accept any number of update operations per
407    but MUST NOT send more than maxOperations update operations in a
413    LDAP update operations from the supplier to the consumer along with
479    supplier to signal that all of the update operations from the
481    to give the results for the update operations from that list.
492    If the status of all of the update operations being reported by an
497    If the status of any of the update operations being reported by an
578    update operations defined in [RFC2251]--Add, Modify, Delete, and
580    semantics of those operations are in effect, so for instance, an
590    update operations.
630    other LDAP operations wherein they are deemed to occur at the
634    Implementations may choose to perform the operations in the update
655    operations and take steps to ensure that only connections with