Adds a stream interceptor to keep state between the send and receive calls #437
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.
Adds an new option
WithStreamInterceptorProviderFunc
where a StreamInterceptorProviderFunc can be specified. With this option a new Stream Interceptor will be created for each new stream created. The Stream Interceptor's Send and Recv functions will be called when a message is sent or received. Unlike theStreamRecvMsgInterceptFunc
andStreamMessageProviderFunc
, the StreamInterceptor can keep state that both Send and Recv functions may need access to.Here is an example of how to use the Stream Interceptor:
`