Clarify expectations for TransportObserver implementations
#2238
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Motivation: `TransportObserver` does not clarify if users can block or not inside their implementations. Modifications: - Copy offloading requirements from `HttpLifecycleObserver` to `TransportObserver`; Result: `TransportObserver` javadoc clarifies expectations for non-blocking implementations and suggests to do manual offloading if necessary.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Motivation:
TransportObserverdoes not clarify if users can block or not insidetheir implementations.
Modifications:
HttpLifecycleObservertoTransportObserver;Result:
TransportObserverjavadoc clarifies expectations for non-blockingimplementations and suggests to do manual offloading if necessary.