![MQL5 - Language of trade strategies built-in the MetaTrader 5 client terminal](https://c.mql5.com/i/registerlandings/logo-2.png)
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
Regarding Sockets and Named-pipes, unfortunately MetaTrader can only act as a "client" and not a "server", so they are not suitable for MQL5 Services.
RAM-Disk based files requires external intervention to set up, so they are not suitable at all.
Memory mapped files can only be created via DLL calls, so it is also not suitable.
The result is that there is no suitable and reliable built-in way for MQL5 Services to communicate and "serve" other MQL5 programs.
Actually I would find a lot more useful to be able to start/stop or check if a service is running (easily) by code then adding/removing it which is the user responsibility (as everything similar on MT5 environment). Of course if we had also the possibility to add/remove a service by code, that would be good, but that's not really something critical at all.
The most important in my opinion would be to have some API to interact with services, from EA, indicators, or other services.
Regarding Sockets and Named-pipes, unfortunately MetaTrader can only act as a "client" and not a "server", so they are not suitable for MQL5 Services.
RAM-Disk based files requires external intervention to set up, so they are not suitable at all.
Memory mapped files can only be created via DLL calls, so it is also not suitable.
The result is that there is no suitable and reliable built-in way for MQL5 Services to communicate and "serve" other MQL5 programs.
The plan to implement Shared Memory has been abandoned.