This repository has been archived by the owner on Oct 30, 2023. It is now read-only.
issue #409 API should allow integration with ExecutorService to allow… #410
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.
#409
When you make an asynchronous call there is no control of how many threads are used for the requests and responses. Particularly when responses are processed the client needs to ensure data integrity, this could be done using synchronization but its better achieved using intelligent threading and dispatching. This is even more important when connecting to more than one exchange and you need to ensure that responses for the same ticker across multiple exchanges are processed in order.
The most simple way to achieve this is to control the threading model for the async calls, rather than relying on the http library.