Ability to shadow an export inside the same transaction

It's very common in OpenERP that with the module extension system, write get called several times upon the same object inside the same transaction. Or it can also be a create followed by one or several writes.

I think we could store the memory id of the transaction (the id of the cr object? any better idea?) inside an export job.

In such case, an exporter may opt-in to choose to abort any export job if it can find another job for exporting the same record_id with the same transaction id. Thus only the last export job of the transaction would be run.

In fact there are system supporting atomic writes and other that don't support it (you always export the full record, this is my case with legacy Apache SolR versions). Aborting jobs is specially interesting for system that don't support atomic writes.
As for the case of atomic writes, eventually record data could be merged: the data of the last job would be merged inside the previous data, that would still save webservices calls.

What do you think?