Never say that. I'm talking about a BOT Context. Not about the world of the REST api Call.
If you read my previous reply i develop by myself in async context.
BUT if we talk about BOT, async response is not useful, i need to get data, i can't continue my work without getting the resul :
Just an example
- If i want to delete an order i must wait for the OK response, because if response is KO i need to find for the trade that fills the order
- I want to have best market prices, i need to call MarketOrders and then get the 2 TOP elements
- I want to create an orders, i need to wait for return code OK and read market ID
Any Calls my bot use need the response.
BUT if you wants to use the MARKET EXPLORER function (that ONLY loads order/trades/myOrder/Mytrader) after you press the LOAD Button, then a dedicated thread will start to popolate the table while you can change screen and continue your work.
This is async BUT, not at API level, because i will perform 4 Sync Call to collect data and then i will show results in 4 tables. So workflow is
UPDATE BUTTON PRESS -> ASYNC THREAD -> 4 SYNC API CALL -> POPULATE TABLES with REsponses.