You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 30, 2023. It is now read-only.
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.
The text was updated successfully, but these errors were encountered:
antlen
added a commit
to antlen/binance-java-api
that referenced
this issue
Jan 5, 2022
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.
The text was updated successfully, but these errors were encountered: