Content Synchronization Operation + Transactions

Hello,

it seems to me that LDAP Transactions (RFC 5805) are not perfectly integrated
into Content Synchronization Operation (RFC 4533).

Mainly the client has no idea what changes were part of single transaction. As
a result, client cannot replicate transactions reliably, especially when
connection drops in the middle of persist phase of Content Synchronization
Operation.

Also some clients could use the information where LDAP transaction
started/ended for application-level transactions (if the application uses the
data in real-time) or possibly some optimizations (if some application-level
work needs to be done after each group of updates).

I'm going to sketch -00 draft which will attempt to address this, probably by
adding new messages to indicate where transaction started and ended.
Naturally, this makes sense only for persist phase.


I would welcome early feedback about this idea even before the -00 is published.

Thank you very much for your time!

-- 
Petr Spacek  @  Red Hat