Discussion of article "Using WinInet.dll for Data Exchange between Terminals via the Internet" - page 5
You are missing trading opportunities:
- Free trading apps
- Over 8,000 signals for copying
- Economic news for exploring financial markets
Registration
Log in
You agree to website policy and terms of use
If you do not have an account, please register
Let it suspend the graph at runtime, what's the problem? I repeat:"the developer can decide when writing a programme whether to use WebRequest or not".
Yeah, for 30 seconds until it times out. And during this time a couple of thousand ticks will accumulate in the OnCalculate queue.
The developer will decide, and it will be impossible to use. If there were no elementary checks in the marketplace, they would put outright inoperable shit. If the language allowed to call web-request from indicators, there would be indicators that hang the terminal. And corresponding reviews would exist.
Yeah, for 30 seconds until it times out. And during that time, a couple of thousand ticks will accumulate in the OnCalculate queue.
The developer will decide, and it will be impossible to use it. If there were no elementary checks in the marketplace, they would put outright inoperable shit. If the language allowed to call web-request from indicators, there would be indicators that hang the terminal. And corresponding reviews.
It hangs for 2-5 seconds, depending on the task. During this time it runs in a loop, collects all the data on positions in an array, forms an array file, and sends screenshots of the chart to the hosting. And this is from 2-5 seconds.
Hangs for 2-5 seconds, depending on the task. During this time it runs in a loop, collects all data on positions in an array, forms an array file, and for those positions that are at the moment - sends screenshots of the graph to the hosting. And this is from 2-5 seconds.
This is realised without hanging the interface, by calling a script, for example.
And with brakes of 2-5 seconds it would be impossible to work with the terminal (make an experiment, it is not difficult).
It is realised without hanging the interface, by calling a script, for example.
And with brakes of 2-5 seconds it would be impossible to work with the terminal (make an experiment, it's not difficult).
I have had it for 1.5 years, the indicator sends data to the site, but using WinInet.dll.
I have had it for 1.5 years now, the indicator sends data to the site
To taste and colour ... all felt-tip pens are different.
It works for you - I'm glad. I don't see the point in changing your mind.
In fact, I myself asked to allow web-request in indicators to send notifications to Telegram. But I've already accepted the fact that it won't happen.
OK, I have changed my mind. This object is worth of try because these sick morons from MetaQuotes forbid using WebRequest function in Strategy Tester.
Hello,
Metachat is a good idea and I'd like to get one working myself.
Nothing referenced on the fxmaster.de site is working anymore - can you please provide the PHP source to metachat? Much thanks.
New article Using WinInet.dll for Data Exchange between Terminals via the Internet is published:
Author: Алексей Сергеев
This article should be seriously edited, the internetLib.mqh included look to be deprecated and can caused a random invalid access in wininet.dll
You should use the internetLib included in this article to avoid difficulties -> Using WinInet in MQL5. Part 2: POST Requests and Files
This library do his work without issues
Good day to you.
I'm currently trying to make use of the wininet for the first time.
I try to make use of you Wininet.mqh but it give me a number of errors, I'm currently trying to solve them. My question to you is "Did you also encounter errors when you did compile the Wininet.mqh file? "
This one fails ec2-18-217-190-217.us-east-2.compute.amazonaws.com
And how to call the script from the indicator? As I know it is also impossible by normal methods.
https://www.mql5.com/ru/articles/5337