Working with data has become the main task for modern software - both for standalone and network applications. To solve this problem a specialized software were created. These are Database Management Systems (DBMS), that can structure, systematize and organize data for their computer storage and processing. As for trading, the most of analysts don't use databases in their work. But there are tasks, where such a solution would have to be handy. This article provides an example of indicators, that can save and load data from databases both with client-server and file-server architectures.
Connect to the server by double checking: to the remote computer named 'RemoteServerName' or to the local computer. On the local one everything works and there are no questions.
But if you run PipeServer.exe on a remote VPS, and then throw the client script to the chart on another PC, having changed RemoteServerName to the name belonging to the VPS, then the server and the client do not see each other, i.e. the channel does not work, there is no connection.
What is the problem here, is it that the name of a particular VPS should be initially written in PipeServer.exe or what?
Connect to the server by double checking: to the remote computer named 'RemoteServerName' or to the local computer. On the local one everything works and there are no questions.
But if you run PipeServer.exe on a remote VPS, and then throw the client script to the chart on another PC, having changed RemoteServerName to the name belonging to the VPS, then the server and the client do not see each other, i.e. the channel does not work, there is no connection.
What is the matter here, is it that the name of a particular VPS should be written initially in PipeServer.exe or what?
I may be wrong.
PipeServer.exe is an ancient technology and has security problems. Today the ports are closed by default in the OS, you need to explicitly allow them. In addition, these ports may be covered by ISPs, if so, you will have to talk to the support team.
If you manage to configure pipelining for remote access, please describe the recipe here. And as a tip, look at the WebRequest function, it can replace pipelining.
Allow the use of cookies to log in to the MQL5.com website.
Please enable the necessary setting in your browser, otherwise you will not be able to log in.
You are signed in. Two-factor authentication has been disabled. Set it up again and scan a new QR code, or continue with two-factor authentication disabled.
Nouvel article Communiquer avec MetaTrader 5 Utilisation des canaux nommés sans l'aide de DLL est publié:
Auteur: MetaQuotes
Hello I can not find file MQL5
Ok, I see. Reported to Service Desk.
You can download this file directly from your MT5 platform. Simply use the search tool with pipeclient keyword.
Ok, I see. Reported to Service Desk.
You can download this file directly from your MT5 platform. Simply use the search tool with pipeclient keyword.
I still don't understand where the __countof function is described
Code::Block swears at it.
I haven't found it in C++ documentation either.
It doesn't compile.
I replaced it with sizeof. It compiled.
I also had to connect three libraries and #define UNICODE
I have a question like this:
The article states:
Connect to the server by double checking: to the remote computer named 'RemoteServerName' or to the local computer. On the local one everything works and there are no questions.
But if you run PipeServer.exe on a remote VPS, and then throw the client script to the chart on another PC, having changed RemoteServerName to the name belonging to the VPS, then the server and the client do not see each other, i.e. the channel does not work, there is no connection.
What is the problem here, is it that the name of a particular VPS should be initially written in PipeServer.exe or what?
I have a question like this:
The article states:
Connect to the server by double checking: to the remote computer named 'RemoteServerName' or to the local computer. On the local one everything works and there are no questions.
But if you run PipeServer.exe on a remote VPS, and then throw the client script to the chart on another PC, having changed RemoteServerName to the name belonging to the VPS, then the server and the client do not see each other, i.e. the channel does not work, there is no connection.
What is the matter here, is it that the name of a particular VPS should be written initially in PipeServer.exe or what?
PipeServer.exe is an ancient technology and has security problems.
Today the ports are closed by default in the OS, you need to explicitly allow them.
In addition, these ports may be covered by ISPs, if so, you will have to talk to the support team.
If you manage to configure pipelining for remote access, please describe the recipe here.
And as a tip, look at the WebRequest function, it can replace pipelining.