Allow usage of RawDataChannel during EngineConnectionState.Intent #4135
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In proxied environment its sometimes useful to allow the communication between the proxy and the backend server before any authentication has begun. For example the proxy can be used to some degree as "source of truth" where it can provide information for sync points, capabilities and other relevant information that plugins might want to process before the
ServerSideConnectionEvent.Auth
begin.While intercommunication trough messaging services should be preferred, sometimes the delay can cause race conditions and the proxy could be used to retrieve the more relevant up to date information on such cases.
This PR allows the following capability by allowing plugin developers to use the
RawDataChannel
duringServerSideConnectionEvent.Intent
and delays the authentication process until no more requests are in-flight. By restricting this to only raw data channels, we can fill this niche use case without more evasive changes to the login process.Open question: