You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Feb 9, 2021. It is now read-only.
This was a leftover from when the fabric transport was string
based. Since we can now send raw bytes, we might as well use
them since its more space and time efficient to avoid the base64
encode/decode cycle.
Change-Id: If1ad0aa0ac0d85a37e6409e8a7ea319a8dbe669f
Signed-off-by: Greg Haskins <gregory.haskins@gmail.com>
Copy file name to clipboardExpand all lines: README.md
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -310,7 +310,7 @@ message ChaincodeInput {
310
310
311
311
}
312
312
```
313
-
Chaintool deterministically maps functions declared within a CCI to an [encoded function name](#function-encoding), and expects the corresponding input parameter to be a base64 encoded protobuf message as the first and only arg string.
313
+
Chaintool deterministically maps functions declared within a CCI to an [encoded function name](#function-encoding), and expects the corresponding input parameter to be a serialized protobuf message as the first and only arg string.
314
314
315
315
Example:
316
316
```
@@ -323,7 +323,7 @@ Function naming follows the convention *interface-name/method-type/method-index*
323
323
324
324
### Output Protocol
325
325
326
-
Standard chaincode protocol allows chaincode applications to return a string to a caller. Chaintool managed applications will encode this string with a base64 encoded protobuf structure (when applicable).
326
+
Standard chaincode protocol allows chaincode applications to return a byte-array payload to a caller. Chaintool managed applications will encode this payload with a serialized protobuf structure (when applicable).
0 commit comments