You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently when doing a protocol communication the callbackAddress is taken from the ProtocolWebhook injectable. This means that at runtime only one protocol is supported. In order to better support multiple protocols and versions in the same runtime a ProtocolWebhook should be configurable for each protocol/version
Which Areas Would Be Affected?
protocol, state-machine
Why Is the Feature Desired?
Are there any requirements?
Solution Proposal
If possible, provide a (brief!) solution proposal.
The text was updated successfully, but these errors were encountered:
Feature Request
Currently when doing a protocol communication the
callbackAddress
is taken from theProtocolWebhook
injectable. This means that at runtime only one protocol is supported. In order to better support multiple protocols and versions in the same runtime aProtocolWebhook
should be configurable for each protocol/versionWhich Areas Would Be Affected?
protocol, state-machine
Why Is the Feature Desired?
Are there any requirements?
Solution Proposal
If possible, provide a (brief!) solution proposal.
The text was updated successfully, but these errors were encountered: