Incoming Block Hooks

[hannahhoward]

Goals

Provide a mechanism to execute hooks on the client side as each block is successfully verified and loaded

Implementation

• Define block hook interfaces
• Modify AsyncLoadResult to identify if request was loaded from local blockstore or from response from network
• Add block hooks infrastructure to requestmanager side -- using same pubsub interface
• Add block hook processing to the request manager & its loader. What this looks like is:
  • Add an extra parameter to the wrapped async loader to run a block hook on each successfully loaded block
  • Refactor setup request to seperate request validation and request processing
  • add an atomic.Value to each inProgressRequestStatus to track the last response received
  • add code to update last response received
  • when each block is loaded, the block hook function in the loader reads the last response for this request, then passes it to the block hooks to process, then takes action based on result
• Add transactions to the response sender -- this allows us to insure groups of response operations are sent in a single response -- fixes an existing bug with block hooks