| | | | Browse by category |
Article ID: 780
Last updated: 05 Feb, 2008
Problem
My RWIFtpClient sometimes hangs, crashes, or does not respond correctly to my commands.
Cause
The most common reason for this random behavior is the use of the
Action
When using the RWIFtpClient methods, you must call the dataClose() method to ensure the thread returns before the calling thread exits. In order to ensure the correct results, the dataClose() method must be assigned to an object whose return value is of the type that RWIOUResult was templatized on.
My RWIFtpClient sometimes hangs, crashes, or does not respond correctly to my commands.
Cause
The most common reason for this random behavior is the use of the
dataClose()
method at the end of the FTP command you are using.Action
When using the RWIFtpClient methods, you must call the dataClose() method to ensure the thread returns before the calling thread exits. In order to ensure the correct results, the dataClose() method must be assigned to an object whose return value is of the type that RWIOUResult
For example, if the RWIFtpClient's dataClose()
member returns an RWIOUResult
RWIFtpReply reply = client.dataClose();not this:
client.dataClose();
Failing to assign the dataClose method to the proper object may result in unexpected behavior.
This requirement is documented in the Tools.h++ Professional User's Guide in section 32.4.
This article was:
Helpful |
Not helpful
Report an issue
Article ID: 780
Last updated: 05 Feb, 2008
Revision: 1
Views: 2638
Posted: 22 Jun, 1998 by
Dean J.
Updated: 05 Feb, 2008 by
Dean J.
Others in this category
Powered by KBPublisher (Knowledge base software)