I solved the problem now (at least mostly) by creating a thread and
assigning the socket to this thread. The execute of the thread is mostly
a message loop.
The normal case now behaves as it should, but if I try to handle a
"emergency" exit command (means not the normal way to quit but some
allow
Hello,
I solved the problem now (at least mostly) by creating a thread and
assigning the socket to this thread. The execute of the thread is mostly
a message loop.
The normal case now behaves as it should, but if I try to handle a
"emergency" exit command (means not the normal way to quit but som
Another new questions, using existing topic.
It's concerning error handling in FTPCli. I see that many local errors, such as
exception when opening local stream, are converted into ftp error messages. How
do I handle them (for example, I want to track file creation errors)? And
another question
> Ok, the "other" application, in this scenario the server has a
> OnDataAvailable event where the first statement is a OutputDebugString
> command so I can see with Sysinternal's DbgView which messages are
> written and which not. In the good case the message can be seen in the
> bad one it's miss
Hello Markus,
Since it happen sometimes it is possible you have some where an
exception that does not show up where you loose data.
Other possibility I see you have a long lineEnd. Can you also test with
1 or 2 character? Maybe you have an untested situation.
---
Rgds, Wilfried [TeamICS]
http://
