Declare the endpoint mode as "historical" in app.json
and access historical state via ccf.historicalState.
This option supports single transactions only and prescribes
how the transaction ID must be passed in the request (via
the x-ms-ccf-transaction-id HTTP header).
The historicalState property provides access to
the historical state of the Key-Value store and information
like the transaction receipt.
Declare the endpoint mode as "readonly" in app.json and use
the programmatic API to request historical state.
This option supports both single and multi-transaction requests.
It also leaves the decision of how to extract the transaction ID(s)
from the HTTP request to the app developer.
The getStateRange function of this module
provides access to a sequential range of transactions.
See the documentation of that function for more details.
This module provides access to historical state.
There are two options to access historical state:
"historical"inapp.jsonand access historical state viaccf.historicalState.This option supports single transactions only and prescribes how the transaction ID must be passed in the request (via the
x-ms-ccf-transaction-idHTTP header). ThehistoricalStateproperty provides access to the historical state of the Key-Value store and information like the transaction receipt."readonly"inapp.jsonand use the programmatic API to request historical state.This option supports both single and multi-transaction requests. It also leaves the decision of how to extract the transaction ID(s) from the HTTP request to the app developer. The
getStateRangefunction of this module provides access to a sequential range of transactions. See the documentation of that function for more details.