TbCS maintains a global monotonic revision counter, incremented exactly once per modifying transaction. Every API response — including read-only get and txn — carries the current value of that counter. Callers commonly need it to drive watchers, retries, and external bookkeeping.
txnResponse.Revision is decoded but discarded — it's only used as a fallback ModRevision per record. tx.Response should carry the global revision directly.
etcd compatibility
Yes — every response carries ResponseHeader.Revision. This brings the wrapper closer to etcd.
TbCS maintains a global monotonic
revisioncounter, incremented exactly once per modifying transaction. Every API response — including read-onlygetandtxn— carries the current value of that counter. Callers commonly need it to drive watchers, retries, and external bookkeeping.txnResponse.Revisionis decoded but discarded — it's only used as a fallbackModRevisionper record.tx.Responseshould carry the global revision directly.etcd compatibility
Yes — every response carries
ResponseHeader.Revision. This brings the wrapper closer to etcd.