File Transfer Control Release Notes

SocketTools 5.0 Build 5035

  • Corrected a problem in the FTP component where an invalid error code could be set for the current thread if the transfer failed under some circumstances.
  • Improved memory management for the FTP and HTTP components for large file transfers, making fewer reallocations and managing the session heap allocated for the transfer more efficiently.
  • Minor corrections to the documentation were made.

Version 5.0 Build 5030

  • Corrected a problem that could result in unexpected errors when attempting to parse the directory listings returned by certain UNIX based servers.
  •  Improved the performance for very large file transfers under some circumstances. The internal algorithm used to recalculate the size of the dynamic buffer used by the transfer algorithm is more sensitive to higher latency network conditions.
  • Corrected a problem that could cause the Reset method to throw an exception under some circumstances, indicating that the product is not licensed, even though a developer license was specified when the component was initialized.
  •  Updated the Developers Guide and Technical Reference and made minor corrections to the overall documentation.

Version 5.0 Build 5020

  • Corrected a problem where the ResultCode and ResultString properties could return incorrect values under some circumstances.
  • Corrected a problem with the License Manager utility that would prevent the control version from being displayed correctly under some circumstances.

Version 5.0 Build 5015

  • Corrected a problem where a malformed resource path could be created if the connection was established through a proxy server. This could result in an error that incorrectly indicated a resource did not exist, even when the resource did actually exist on the server.
  • Modified the control to support active mode file transfers over secure connections. In previous versions, the connection would always be forced into passive mode for secure connections, regardless of the value of the Passive property.
  • Modified the control automatically select an explicit SSL session if the Secure property is set to true and the connection is established on the standard service port number (21).
  • Modified the control to permit a maximum timeout value of greater than 600 seconds. The maximum timeout value is now 86,400 seconds (24 hours).
  • Updated the Developer's Guide and Technical Reference documentation. Corrected an issue with the installation which did not include a shortcut to the PDF version of the documentation.

Version 5.0 Build 5010

  • Corrected a problem where certain security constants were defined incorrectly in the interface definition for the components.
  • Updated the support library which implements the trace logging facility, reducing some extraneous detail being included in logfile under certain conditions. This would typically manifest as a single Windows Sockets API call being logged multiple times.
  • Updated the Developer's Guide and Technical Reference documentation with current build information and minor corrections.

Version 5.0 Build 5000

  • Updated for full compatibility with the Windows Vista platform, supporting the new security model and TCP/IP stack.
  • Core networking code updated to use Windows Sockets 2.2 API and removed all dependencies on Windows 95/98 TCP/IP stack.
  • Redesigned the memory management code used to allocate buffers and private data structures for client sessions, improving performance and reducing overhead when multiple sessions are created in a multithreaded application.
  • Added support for AES (Advanced Encryption Standard) encryption for secure SSL/TLS connections on Windows Vista.
  • Added the ActivePort property array to enable the developer to specify the active port range to be used when transferring files.
  • Corrected a problem with the where automatic proxy detection may fail unexpectedly or not select the correct proxy configuration.
  • Modified the the control to automatically correct invalid resource paths that may be specified by the caller.
  • Modified the Connect method to automatically attempt to a direct connection to the server if the default proxy could not be accessed for some reason. This is designed to primarily include reliability where the client system may have an invalid or incomplete proxy server configuration.
  • Corrected a problem where the SSL/TLS handshake may not complete correctly under high latency situations, and would not return the correct error code if it failed.
  • The FileStatus method has been deprecated and should no longer be used and the GetFileStatus method should be used instead.
  • The GetFile and PutFile methods in the FTP and HTTP components will automatically establish a connection if the remote file name is a complete URL and no connection already exists. The GetResource and PutResource methods have been deprecated; however, they may still be used by applications for backwards compatibility with source written for an earlier version of the control.

File Transfer Links

Product Overview
An overview of the product design, features and benefits.

Product Features
Additional information about the product features.

.NET Component
Information about the File Transfer .NET component.

ActiveX Control
Information about the File Transfer ActiveX control.

Frequently Asked Questions
Answers to the most common questions about the product.

Release Notes
Release notes for the current version of the product.

License Agreement
The developer license agreement for this product.