![]() |
| FTPCOM | ||
| An FTP Client Library |
| If you have any questions about our open source programs, or wish to obtain more information on our products, then please send a message to OpenSource@artige.com and we will be happy to handle your request. | ||
| FTPCOM is an FTP client library. Unlike the typical FTP user agent that imposes upon the end user a single approach to handling file transfers, the FTPCOM library provides the programmer the tools to create one 's own FTP client. You can use it to help you create your own full blown GUI, web accessible object or deployed from a native service. The FTPCOM library allows direct access to all of the FTP commands, as defined by RFC 959. This way one can write and customize their own FTP programs, making it as small or as big as your requirements need. Since the FTPCOM library is offered under the LPGL open source license, there are no fees to pay, and no complex or changing EULAs to be trapped under. You can even modify the means that the FTP code is deployed to your heart's content, as the source code has been provided as part of the library. | ||
| The FTPCOM library is being offered under open source license, so that it could be used by anyone, and extended by the user as desired. | ||
| Available on this page: | Background | Downloads |
| Background | History | |
| The stimulus for this project was a customer requirement to automatically exchange files in a secure manner with a proprietary FTP server. The vendor of the FTP proprietary program provided a buggy, single threaded client that was GUI based. Our customer had originally interfaced with the proprietary FTP server by launched the GUI client via Microsoft's "AT" scheduler. Between the unreliability of the AT scheduler, the bugginess of the proprietary FTP client, and the lack of logging functionality in the proprietary FTP client, our customer was unable to maintain a stable transaction environment, resulting in business difficulties and incurring penalties. So we were called in to clean up the mess and provide a reliable file exchange mechanism, with the caveat that the proprietary FTP server had to stay. | ||
| Lucky for us, the vendor of the proprietary FTP server did offer a non- proprietary access method that relied upon TLS FTP that we could use. This way we no longer had to rely upon their buggy FTP client. So we opted to use that alternative method. Of course it was not straightforward, as the TLS based FTP protocol was not yet finalized. There were not many vendors out there with an FTP library that supported TLS. On top of that, most FTP clients that did provide TLS were fat GUI programs. There are some lean FTP libraries for sale, but we could not locate an open source FTP client library that also provided TLS functionality. Subsequently, we ended up purchasing an FTP library. Burned only once we say, so to make sure that never happened again, we elected to write our own open source FTP library, in our spare time. FTPCOM is the result of that endeavor. | ||
| The Library | ||
| The FTPCOM library has implemented some portion or the entire FTP related RFCs. Over time, we plan to complete the RFC implementations in their entirety, as tabulated below: | ||
| Number | Title | Implementation Status | |||
| RFC - 959 | File Transfer Protocol (FTP) | Fully implemented | |||
| RFC - 2389 | Feature Negotiation Mechanism for the FTP | 50% implemented | |||
| RFC - 2228 | FTP Security Extensions | Not yet implemented | |||
| RFC - 4217 | Securing FTP with TLS | Not yet implemented |
| As the library currently stands, one can perform basic FTP functions without the ability to invoke any secure transport method. Once completed, the library will support the secure transport methods. | ||
| We will be providing the FTPCOM library as an immediately usable Windows DLL file. Since we are offering the library under the LPGL license, we are also offering the source code. Finally, we will also be providing a Visual Basic V6 program to exercise the library, so one can see one method of using the library. | ||
| Downloads | Prerequisites: | |
| 1- 32 bit Windows* operating system (Windows NT, Windows 2000, Windows XP, Windows 2003) | ||
| Currently we are providing files for 32 bit Windows* operating systems. These programs will probably not work on Windows* ME, Windows* 98 or any of its 16-bit predecessors. Also, we have no idea if the library will work on a 64 bit Windows* 2003 server, so we will not make any claim that it will work on a 64 bit OS. | |||
| Note: At this time we are focusing on delivering the FTPCOM library to developers, who should know how to work with DLLs, and have the developer tools from Microsoft, including any ancillary files the libraries or test programs require. Therefore, we are not providing an installer at this time for any of the below files. The same goes for handling privileges, a developer should already be aware for any need to elevate privileges when working with these files. | |||
| Version 0.6.0 Library - 32 bit Windows* Latest |
This zip file contains the DLL and the TypeLib files to load onto a Windows* NT, Windows* 2000, Windows* XP or Windows* 2003 workstation or server that will run the FTP library. Just save the zip file to a directory with sufficient privileges for the task and unzip it. You may need to run regsvr32 in order for the COM system to recognize the library. | ||
| Version 0.6.0 Source - VS6 Latest |
This zip file contains the Visual Studio 6 project that was used to create the FTPCOM Library (FTPcom1.dll). It includes only the main project source folder with most of their contents. It does not include any of the generated debug or release folders, nor the very large precompiled headers. We will let you generate those yourself. | ||
| * - Windows is a trademark of the Microsoft Corporation. | |||
| Return to open source page | Navigate to home page | ||
| All rights reserved. |
All site content copyright © 1997-2007 Artige Company
|
| Last updated: 5-February-2007 21:33z |