Discussing the article: "Developing a Replay System (Part 73): An Unusual Communication (II)"

 

Check out the new article: Developing a Replay System (Part 73): An Unusual Communication (II).

In this article, we will look at how to transmit information in real time between the indicator and the service, and also understand why problems may arise when changing the timeframe and how to solve them. As a bonus, you will get access to the latest version of the replay /simulation app.

In the previous article "Developing a Replay System (Part 72): An Unusual Communication (I)" I began to show how you can use an indicator to transmit certain information that would otherwise be impossible to obtain. ]Although I provided a number of explanations in that article, actually implementing the code in our replay/simulator application is not quite that simple. You may be thinking that I'm just being dramatic. That implementing such functionality is quite simple and clear. That I'm just building suspense for effect.

Well, I wish I were simply building suspense around this topic. But the truth is, this really is far more complex than you might initially imagine. I've made a conscious effort to make these articles understandable to all those who really want to learn MQL5. And the current topic, at least up to the time of writing this article, is something I haven't seen anyone explore. Not because it's unthinkable, but because it's at the very least quite exotic and highly uncommon. That's why I'm trying to highlight as many details as possible about how you should proceed when tackling something for which no precedent exists.


Author: Daniel Jose