Off-Chain Protocol: Optional Result Field about dip HOT 4 OPEN

One doesn't have to do a subsequent JSON-RPC query to get a result that's more informative than just status: success. In this case, the desired information is the recipient_address normally in a ReferenceIDCommand. By having it in a result field, it saves a second round trip, simplifying and reducing latency for a P2M flow.

Put another way, one can issue a command and get the response in a single JSON-RPC command as opposed to two: doAction, getRecipientAddress.

from dip.

I don't understand what makes embedding a result field in a response "synchronous", could you explain?

from dip.

Thanks for the explanation @dimroc . This makes total sense, but the terminology "asynchronous/synchronous" don't apply here. I would remove them, and just leave the explanation that a response field can include information that may prevent the need for another message exchange.

from dip.

Hi @dahliamalkhi i've incorporated your feedback into the PR for this dip #165 if you can take a look that'd be great!

from dip.