Highly reliable transaction/signal copier (ideology discussion and development) - 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
I've been doing a little digging around. Examples of simple client-server systems in different languages.
and in a nutshell, what's your proposal?
- Is synchronization done over a socket?
- The full state of the master account is transmitted?
and in brief, what kind of proposal are you making?
- does synchronisation happen over a socket?
- is the full state of the master account transmitted?
And outline the server-client context, where does the server stand where the clients stand?
Sorry to run out, I'll be back in an hour.
What about server-client context, where does the server stand where the clients stand?
ok. let's narrow it down further.
we have a remote server to which the wizard sends its data.
Clients are also connected to the same server.
The question is what method is used for receiving/transmitting information. From the current suggestions socket/http/ftp
what are the pros and cons of these technologies for server load and traffic?
OK. Let's narrow down the problem further.
We have a remote server to which the wizard sends its data.
Clients are also connected to the same server.
The question is what method is used for receiving/transmitting information. From the current suggestions socket/http/ftp
What are the pros and cons of these technologies for server load and traffic?
Socket over TCP/IP. It is possible to transmit signals in text form in one line per signal, such as "EURUSD Buy 1.0\n", as via Telnet, because this is the most primitive version that does not require complex exchange procedure, as in http or ftp protocols with minimum parsing.
The problem is that the server must be multi-threaded, otherwise how can it simultaneously receive connections from clients? It has to listen to its own socket on the allocated port all the time and in case of connection transfer a client to another free port and allocate a separate thread to it. Then he has to wait for another client on the main port.
ok. let's narrow down the problem further.
we have a remote server to which the master sends its data.
Clients are also connected to the same server.
The question is what method is used for receiving/transmitting information. From the current suggestions socket/http/ftp
Pros and cons of these technologies for server load and traffic?
Socket, http/ftp just gives access to remote files, whereas socket is a data exchange protocol.
A socket is not a protocol. A socket is a socket, i.e. the kind of thing on a port that receives and transmits data. A socket can be a server socket and must have a fixed port on which it listens. And there is a client socket that connects to servers using the server IP and port number.
And FTP, HTTP, Telnet are protocols. Files can be transferred using all three of these protocols. But telnet is a streaming protocol, not a one-time thing, that's why clients can hang on it as long as they want and when a trade signal appears they can get it immediately. With the other protocols, you would have to mess up the server socket all the time to find out if there is a signal or not, and then fall off.
A socket is not a protocol. A socket is a socket, i.e. the kind of thing on a port that receives and transmits data. A socket can be a server socket and must have a fixed port on which it listens. And there is a client socket that connects to servers by IP and server number.
And FTP, HTTP, Telnet are protocols. Files can be transferred using all three of these protocols. But telnet is a streaming protocol, not a one time protocol, that's why clients can hang on it as long as they want and when trade signal appears they can get it immediately. With the other protocols, you would have to mess up the server socket all the time to find out if there is a signal or not, and then fall off.
Are there any examples for Telnet ? very interesting.
https://ru.wikipedia.org/wiki/Telnet
I've seen it before the question, it's hard to call it an example of use, but thanks anyway, it's an interesting idea, I'll have to dig around.
It is essentially a text-based protocol. But it is mainly used for remote Unix connections on port 23. That is, you can log in to a remote Unix server with your username and password and execute operating system commands.
In a simplified form, telnet can be used for anything, including the transmission of trading signals as single-line messages. I.e. no commands or anything else. The client connects and waits for the server to send the signal. He receives, passes it, opens or closes a position and waits for the next signal. That is the whole protocol.