[FAB-8014]add cross channel chaincode invoke doc

Corrent doc about chaincode invoke from different channel is inconsistent with the InvokeChaincode() API. this RC updated the corresponding doc. https://jira.hyperledger.org/browse/FAB-8014 Change-Id: Id3b63f7f63f59ec04e9fe563e40c93abb785a9dd Signed-off-by: Min Luo <[email protected]>
hyperledger · Feb 6, 2018 · 96410aa · 96410aa
1 parent d0690ce
commit 96410aa
Showing 1 changed file with 6 additions and 4 deletions.
diff --git a/docs/source/chaincode4ade.rst b/docs/source/chaincode4ade.rst
@@ -11,10 +11,12 @@ the endorsing peer process. Chaincode initializes and manages the ledger state
 through transactions submitted by applications.
 
 A chaincode typically handles business logic agreed to by members of the
-network, so it similar to a "smart contract". Ledger state created by
-a chaincode is scoped exclusively to that chaincode and can't be accessed
-directly by another chaincode. Given the appropriate permission, a chaincode may
-invoke another chaincode to access its state within the same network.
+network, so it similar to a "smart contract". A chaincode can be invoked to update or query 
+the ledger in a proposal transaction. Given the appropriate permission, a chaincode 
+may invoke another chaincode, either in the same channel or in different channels, to access its state. 
+Note that, if the called chaincode is on a different channel from the calling chaincode,
+only read query is allowed. That is, the called chaincode on a different channel is only a `Query`,
+which does not participate in state validation checks in subsequent commit phase.
 
 In the following sections, we will explore chaincode through the eyes of an
 application developer. We'll present a simple chaincode sample application