How do you ensure that websocket multi-currency request connections receive price pushes?
Author: [Translated from Chinese], Created: 2021-11-09 14:43:18, Updated:
I use this link to get the price of the multi-currency.
Then, in the while loop, stream.read (((-2) is used to get the price of each currency, but the price obtained is not the same frequency and is not in order.
For example, in the graph, you can get 3 LTCs and get 1 BCH, and I'm wondering if there's a situation where there's a lot of currencies that don't get the price?
For example, LTC, LTC, BCH, ETH, LTC, LTC, BCH and then keep missing the price update of a certain currency.
I'm not sure if I'm using it correctly or not. How can I fix it?
I know there's a price to get all the currencies, but I thought it might be faster with a multi-currency link.
- _D ((Timestamp, Fmt) function to change the default format
- Do you have to be an integer to open a position?
- How can I get a list of currencies supported by the exchange?
- Binance websocket subscribe bookticker how is the data so slow
- Logs are pushed to Telegram
- How to use pythonIDE for policy debugging?
- You can solve problems for free, teach friends, and write strategies.
- It is becoming increasingly difficult to quantify individual work, but it is still important to have a team.
- fmz_extend_api_demo build problem please
- Continue to ask questions about access to account information
- The inventor's website is careful, and the app has found it too.
- Access to account information
- Looking for a real-time quantification strategy for 0.7% of the market
- Commodity futures, strategic retesting, not adding an exchange?
- Problems with Strategic Testing
- Problems with analog discs
- OKEX has access to account information
- How to recommend a good strategy
- Please help me to see the problem of ema cross-signals.
- Do you have a template for the community's interest rate policy?
Spartan play quantifiedDon't use two.
Spartan play quantifiedread ((-1) can get data in arrival order
The Little DreamWS interfaces are pushed by exchanges, which are specifically related to the push of exchanges, uncertain.