Issue 10812: Cancel transaction (data-distribution-rtf)
Source:  (, )
Nature: Uncategorized Issue
Severity: 
Summary: Problem:
It is possible that a transaction needs to be canceled, for example because one of the participating writers gets blocked and finally stops while returning a timeout. This might lead to the situation in which you want to cancel all preceding writes as well.

Solution:
To be able to cancel such a transaction, we propose to add an additional operation like e.g. cancel_coherent_changes would then remove all samples that have already been written since the last begin_coherent_changes.

Resolution: 
Revised Text: 
Actions taken:
March 5, 2007: received issue
Discussion: 

End of Annotations:=====
s is issue # 10812	From: "Robert Poth" <Robert.Poth@prismtech.com>


Cancel transaction

Problem:
It is possible that a transaction needs to be canceled, for example because one of the participating writers gets blocked and finally stops while returning a timeout. This might lead to the situation in which you want to cancel all preceding writes as well.

Solution:
To be able to cancel such a transaction, we propose to add an additional operation like e.g. cancel_coherent_changes would then remove all samples that have already been written since the last begin_coherent_changes.