Were the Socket* functions removed from MQL5?

 

When I try to use any of the socket functions like SocketCreate() which are documented in the Network section:

https://www.mql5.com/en/docs/network

I get the error message "function not defined" in the MetaEditor when it tries to compile it. Do these functions need a special include if you want to use them or were they removed from MQL5 for some reason?

I found articles on mql5.com about other socket libraries, but I think it would be great if the documentation was in sync with the MetaEditor functionality.

Thank you for any feedback!

Documentation on MQL5: Network Functions
Documentation on MQL5: Network Functions
  • www.mql5.com

  • The Socket* group of functions allows establishing a TCP connection (including a secure TLS) with a remote host via system sockets. The operation principle is simple: create a socket, connect to the server and start reading and writing data.

For end-user security, the list of allowed IP addresses is implemented on the client terminal side. The list contains IP addresses the MQL5 program is allowed to connect to via the Socket* and WebRequest functions. For example, if the program needs to connect to https://www.someserver.com, this address should be explicitly indicated by a terminal user in the list. An address cannot be added programmatically.

Add an explicit message to the MQL5 program to notify a user of the need for additional configuration. You can do that via #property description, Alert or Print.

Documentation on MQL5: Network Functions
Documentation on MQL5: Network Functions
  • www.mql5.com
The Socket* group of functions allows establishing a TCP connection (including a secure TLS) with a remote host via system sockets. The operation principle is simple: create a socket, connect to the server and start reading and writing data. For end-user security, the list of allowed IP addresses is implemented on the client terminal side. The...
 
Interesting topic. It would be great help if socket creation is available mql.
 

Normal sockets are blocking on one side.

I am convinced that writing files on a RAM-Disk with the Win-File-Functions is fast and a lot easier:

The writer (sender) blocks and writes the file, the reader (receiver) first checks the file existence and blocks, read and deletes the entire file.

Simple and fast.

 
Carl Schreiber:

Normal sockets are blocking on one side.

I am convinced that writing files on a RAM-Disk with the Win-File-Functions is fast and a lot easier:

The writer (sender) blocks and writes the file, the reader (receiver) first checks the file existence and blocks, read and deletes the entire file.

Simple and fast.

I agree but thing is that these socket apis are removed? or yet they are work in progress?

There are other applications of socket which are not possible using filing system.

Reason: