Hello,
I've some big problems with the telnet components, the biggest one being
the lack of documentation.
What I want to do is the following:
1. start a telnet session (that one works)
2. have a list of commands
3. loop through the list and carry out one command after the other
4. display
When do I need, or would I want, to call Shutdown(), and what are the
ramifications of the different parameters that one can pass it.
I see Shutdown(2) in one of the demo apps, but don't know what 2
represents.
The information transmitted is intended only for the person or entity to
which it
I will be receiving a variety of structs/records, all of different sizes and
makeups.
How can I (in the OnDataAvailable() handler, I assume), determine/identify
which record has just come in, so that I can process it accordingly?
OnDataAvailable() should only fire once for each record,
David A. G. wrote:
Hello all:
I'm having problems SmtpCli where OnRequestDone function is not fired
after sending QUIT command because the SMTP server is not closing the
connection!!.
We've been talking this topic many times.
The RFCs say that the server has to close the connection, so if
Francois PIETTE wrote:
(3) In the code running after a failed download I'm removing the last
portion of the received data, just in case it's corrupted. I noticed
this behavior in a freeware download manager I used to use some time
ago. But now I'm asking: is this really necessary? HTTP traffic
In my opinion, the servers are not compliant with the standard. Indtead of
tweaking the component, either simply colse the connection yourself or
implement a timeout and close it later if the server don't do it quickly
enough for you.
Contribute to the SSL Effort. Visit
I think TTnScript is the way to go. You can dynamically add/remove events
according to which screen you detect. If you don't use TTnScript, has a
look at his source code to understand how to get hand on the input stream to
chack for data.
I also uploaded a modified version of the components. It
I am trying to test sending records from a utility to my app, which should
receive and process the records.
I am able to send the record from my test utility with this code:
procedure TForm10.btnSendMsgAsRecordClick(Sender: TObject);
begin
InitializeWSocketProperties;
We've been talking this topic many times.
The RFCs say that the server has to close the
connection, so if
a server doesn't close the connection on receiving
command QUIT
the server is buggy. You can handle those
server-side bugs with a simple
command timeout, in real applications some a
