-
Dinesh Kumar authored
FSM was needed to manage concurrent Queries and serial Invokes in 0.5/0.6. There are no Queries in 1.0+ and Invokes are concurrent. Hence FSM can be removed entirely greatly simplifying the chaincode component. Note that Shim FSM does not depend upon fabric FSM. Hence Node and Java CC support can remove Shim FSMs in their own time. Phase 1 just removes FSM and makes sure both old and new code share parity. We might do a Phase 2 to streamline the code further (but not essential). patch 1 . remove "trigger" funcs as all they do is send now . introduce "nextState" call to handle serialization of ready (the generalization could be useful) Change-Id: I526d3041bedfeefc00d34e1e53a4e7465aa99584 Signed-off-by:
Dinesh Kumar <dinesh.kumar@itpeoplecorp.com> Signed-off-by:
Srinivasan Muralidharan <srinivasan.muralidharan99@gmail.com>
Dinesh Kumar authoredFSM was needed to manage concurrent Queries and serial Invokes in 0.5/0.6. There are no Queries in 1.0+ and Invokes are concurrent. Hence FSM can be removed entirely greatly simplifying the chaincode component. Note that Shim FSM does not depend upon fabric FSM. Hence Node and Java CC support can remove Shim FSMs in their own time. Phase 1 just removes FSM and makes sure both old and new code share parity. We might do a Phase 2 to streamline the code further (but not essential). patch 1 . remove "trigger" funcs as all they do is send now . introduce "nextState" call to handle serialization of ready (the generalization could be useful) Change-Id: I526d3041bedfeefc00d34e1e53a4e7465aa99584 Signed-off-by:
Dinesh Kumar <dinesh.kumar@itpeoplecorp.com> Signed-off-by:
Srinivasan Muralidharan <srinivasan.muralidharan99@gmail.com>
Loading