[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: commit: ldap/servers/slapd/back-bdb search.c

The cancel exop is provided as a groundwork for LDUP-SYNC
synchronization operation, but as it manifest by itself, I've committed it
For other operations such as add and modify,
the cancel exop seems to have more sense in bdb,
because operations can be undone at any time before transaction commit
by aborting the surrounding transactions.
For other backends, how about checking the cancel flag at the same point in
where the abandon flag is checked ?
- Jong

Jong Hyuk Choi
IBM Thomas J. Watson Research Center - Enterprise Linux Group
P. O. Box 218, Yorktown Heights, NY 10598
email: jongchoi@us.ibm.com
(phone) 914-945-3979    (fax) 914-945-4425   TL: 862-3979

"Pierangelo Masarati" <ando@sys-net.it>@OpenLDAP.org on 01/27/2003 03:09:06

Please respond to ando@sys-net.it

Sent by:    owner-openldap-devel@OpenLDAP.org

To:    <jongchoi@OpenLDAP.org>
cc:    <openldap-commit2devel@OpenLDAP.org>
Subject:    Re: commit: ldap/servers/slapd/back-bdb search.c

> Update of /repo/OpenLDAP/pkg/ldap/servers/slapd/back-bdb
> Modified Files:
>     search.c  1.96 -> 1.97
> Log Message:
> LDAP cancel operation

BTW, do you intend to apply the cancel exop also
to other operations in bdb, and to other backends?


Pierangelo Masarati