@backtrader Thanks for your detailed reply.
As pointed out above: if the store you work with makes direct requests to the network as a result of an action initiated by the Strategy (hence ... blocking the main thread), the design is wrong.
My focus is crypto currency and I work with the community driven development that tries to bind between Backtrader and CCXT project (which play the broker roll).
but as you mentioned broker and store doesn't include threading to keep all the data well updated, instead it use cache or direct network calls.
which made me wonder how to run strategies in that setup.
clearly for it to work as intended in Backtrader more work on both store and broker is needed.
Ok, so just to see if I understand the concept, at the most simple level.
we expect from the store to take control over updating some of the data independently of what is going on in backtrader using a thread for each thing we wanna keep updated. so for example, as the store get instantiated we will need to create a thread that keep account details up to date at all time. so when we call it from the strategy we get the latest values from the cache.
just trying to connect the dots with the information I read.