Conversation
Signed-off-by: Gabriel Indik <gabriel.indik@kaleido.io>
Signed-off-by: Gabriel Indik <gabriel.indik@kaleido.io>
Signed-off-by: Gabriel Indik <gabriel.indik@kaleido.io>
Signed-off-by: Gabriel Indik <gabriel.indik@kaleido.io>
|
Changes included in this PR: Note that Data Exchange automatically associates destinations with peer information. This is for optimization purposes. More specifically, Data Exchange will not create multiple copies of the same certificate file. Instead each certificate will continue to be associated with a peer, and each peer can have 0-to-many destinations. Similarly to how peers work, one can optionally pre-populate destinations in the Data Exchange configuration file for both sender and recipients (see changes in the configuration schema and sample config files). When invoking the With these changes any call with an unknown destination on either the sender or the recipient will raise an error. The error messages are very detailed, showing what the valid destinations are (for sender and/or recipient) and which one was provided. Finally, backward compatibility is preserved, making it possible to use Data Exchange seamlessly with and without destinations. |
| if (recipientURL === undefined) { | ||
| throw new RequestError(`Unknown recipient`, 400); | ||
| let recipientEndpoint: string; | ||
| recipientEndpoint = config.p2p.endpoint ?? `https://${config.p2p.hostname}:${config.p2p.port}`; |
There was a problem hiding this comment.
This looks wrong... maybe this was supposed to be inside the if below?
|
Updated PR: #67 |
No description provided.