The main problem with Telnet is that it does NOT use the command / response model, as most other Internet protocols do. Any party can send data at any time, and each data direction is independent of the other direction. This is reflected in the TIdTelnetfact that an internal read stream is performed to receive data. Because of this, you cannot just connect, send a command and wait for an answer in one block of code, as you can, with other Indy components. You have to write a command and then wait for an event OnDataAvailableto trigger, and then analyze the data to determine what it really is (and be prepared to handle situations where partial data can be received, since that is how TCP / IP works.)
, /, TIdTCPClient TIdTelnet ( Telnet , Telnet, , ). Indy 11 TIdTelnet - , .