Re: draft-ietf-ldapext-ldapv3-txn-00.txt More ..

[Satoshi Kikuchi <s-kikuti@sdl.hitachi.co.jp>]

David Boreham wrote:
> 
> Perhaps a list of operations where transactions
> are considered useful is needed ?
> 
> The document mentions two:
> 
> (1) maintaining a counter in an entry (eg software
> license count).
> (2) Two entries who's contents need to be kept
> in some strict relationship (eg an entry and its certificate).
> 
> Here are two more above.
> 
> Anyone have any others to add ?

Administrators often use online applications and batch programs, to
maintain directory information.  The batch program will continuously
update directory entries in bulk.  Such program is required to rerun
those updates for the recovery from catastrophic failures during the
batch cycle.  However, it would be too complex to rerun because those
requests have been partly done in ordinary server.

A transaction could treat multiple requests as an atomic operation (in
all or nothing manner), so it is helpful for the above program.  When
the program reruns, it will be able to be done again from the beginning.

We believe that users need LDAP transactions in operational directory
environments.  Actually, we took the requirement from our customers.  In
order to satisfy the practical requirement, we have implemented
transactions in LDAP as a commercial solution.

Regards,
Satoshi