This repository has been archived by the owner on May 1, 2024. It is now read-only.
[wip]: Native Receive #661
Draft
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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
This is the start to be able to enabled native transport receive in #629 . The changes have one purpose so far: Remove the need to call
IReceiverCallbackfrom theIListenerimplementations and move it up a level into the Worker Queues. This allows theIListenerimplementations to be very thin and only deal with receiving messages from the transport and doing ack/nacks. By centralizing the calls toIReceiverCallbackit should make implementing additional transports easier in the future as the author will not need to worry about dealing with it.All functionality of Jasper should be exactly as it was from a functionality standpoint. This just sets things up to be able to implement native receive functionality.