Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Multiprotocol DSP path #4711

Open
wolf4ood opened this issue Jan 10, 2025 · 0 comments
Open

Multiprotocol DSP path #4711

wolf4ood opened this issue Jan 10, 2025 · 0 comments
Assignees
Labels
enhancement New feature or request

Comments

@wolf4ood
Copy link
Contributor

Feature Request

Currently for out going messages a connector takes the counterPartyAddress and append the path based on the chosen dsp protocol version which is configured in the connector. This might not be the case when communicating with a different dsp implementation which might expose protocol version under different paths.

Since EDC now expose the management api for fetching supported DSP version from a counter party we should let the users decide the base path of the dsp version (counterPartyAddress + dsp version path) directly in input, without automatically infer that.

Meanwhile for the callbackAddress which currently comes from ProtocolWebhook should automatically infer and append ther dsp version path based on the connector supported version in the ProtocolVersionRegistry

To keep the current behavior we might introduce a configuration flag which should be disable by default.

Which Areas Would Be Affected?

dsp

Why Is the Feature Desired?

interoperability

@wolf4ood wolf4ood added the enhancement New feature or request label Jan 10, 2025
@wolf4ood wolf4ood self-assigned this Jan 10, 2025
@github-actions github-actions bot added the triage all new issues awaiting classification label Jan 10, 2025
@wolf4ood wolf4ood removed the triage all new issues awaiting classification label Jan 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant