Exec RPC has to become async friendly, broker like API in order to survive client disconnections.
Once a client disconnects, they should be able to resume consuming outputs from the last event at reconnection. Today, we allow client to backfill from a last_seq but it's not sufficient because Substrate deployments will reject a backfill request while the conversation is already in flight, and client can only fill after the last execution is completed or failed.
Exec RPC has to become async friendly, broker like API in order to survive client disconnections.
Once a client disconnects, they should be able to resume consuming outputs from the last event at reconnection. Today, we allow client to backfill from a last_seq but it's not sufficient because Substrate deployments will reject a backfill request while the conversation is already in flight, and client can only fill after the last execution is completed or failed.