Redesign wait on BAP-Client on return leg of point to point request

[vbabuEM]

In the return leg of Select and other P2P request, there is a 100ms timer that results in a variable delay of less than 100ms in the BAP Client. Redesign the Protocol Server to remove this delay and make the return immediate.

[shreyvishal]

Current Status:
Have Worked on this and below are my observations and Suggestion:

• Observation
  Currently when the BAP-Network receives the on_action response from the BPPs then it stores the data to mongoDb instance that is used for caching by both BAP-Client and BAP-Network, and there is a setInterval for 100ms running on BAP-Client checking for the response received

• Suggestion
  Instead of storing the the response coming from BPP to the mongoDb cache we can send that response to the message queue from the BAP-Network and the BAP-Client will listen on that queue and will receive the response send it directly to the Client

cc: @vbabuEM

[vbabuEM]

This has to be synchronous response on the client side. How will you achieve that with the Suggestion?
@shreyvishal