As a system administrator I need the composer-rest-server to tolerate unavailable peers #2799
Composer currently handles responses that could not be sent to the peer, but currently still doesn't do anything around event handling or query chaincode. Here are the issues that need to be considered.
A rethink of how to listen for transaction completion events needs to be done because not receiving the event doesn't mean that the transaction didn't complete. We need to think about the following
We would also want to do something similar for the business event emission as well except it should only register one listener for the first event hub that allows it.
Some of this is likely to be something the fabric node sdk should handle rather than composer and also needs to be considered within the context of the Common Connection Profile implementation coming in fabric 1.1