Chris Sellers

So there's been some progress, I've managed to consolidate the steam between sync and async method for connecting, disconnecting and the main execution methods. The idea here is that an...

Just squeezing out a small update for this. - We continue to push down boilerplate into the client base classes, that's been progressing well - We've also been making some...

Hi @pontus-lund Thanks for the feedback here. Were you aware of the `CacheDatabase` facade/interface, which just needs implementing to add different underlying technologies, I think then all we would need...

Hi @pwyngaard Thanks for reaching out, this is definitely an interesting use case for the platform. I've discussed with @limx0 and we think there's a chance that everything you need...

This suggestion seems quite reasonable. @pwyngaard would this meet your needs if it was implemented?

I see that they are implemented though? so the intent of those methods is to aid serialization (starting with a Python dict of 'primitives' makes things easier here) - so...

I like this direction, and the functionality is definitely needed. I believe the main use case here is for continuous trading, we want to avoid an unbounded increase in memory...

> So were you thinking a strict max look-back applied on the database side? How would this work for dependent objects such as the events that are part of a...

@rsmb7z I just need a little more information and context to help here. How are you currently handling revised bars in the strategy, to prevent them updating the indicators? Would...

With the flow charts you provided, if you wanted to take different actions in the strategy depending on whether the received bar is a revision, could you not also do...