Support different scenarios of when a chaincode is executed about fabric HOT 4 CLOSED

@prjayach @muralisrini This one doesn't look like an executable issue. Would you mind rewriting it or close if no longer applicable? All 3 cases, I see, at the end, a tx invoke will be carried out.

from fabric.

The cases are applicable if at some point we support events natively. An event can be a signed message that signifies a real-world occurrence (e.g., shipment delivery). Multiple contracts may be interested in an event and may trigger transactions based on them. I think this will greatly simplify development of smart contracts, as events are a fundamental notion in any smart contract. With this support, a smart contract can just say 'On event E, invoke chaincode X'; no single entity will be in charge of invoking the transaction, but the system as a whole will automate that execution.

from fabric.

To continue the shipment example, when shipment is completed (an event occurs), neither the buyer nor the seller needs to explicitly invoke the payment transaction. It will be automatically triggered; in fact, neither the buyer nor the seller will have the ability to refuse initiation of the payment transaction once the contract has been agreed upon and deployed on the ledger.

from fabric.

@muralisrini it can't go to milestone 2, which has been over 2 weeks ago. I am putting this issue back to backlog until someone can work on it. It is not MVP

from fabric.