This project has declared the following modules:
| Name | Description |
|---|---|
| Waarp Digest | This project allows support of Digest (MD5, SHA1, CRC) for Commons Waarp project. |
| Waarp Common | The Waarp Common project contains several classes that are common with different sub projects of Waarp (FTP, R66, ...). Mainly there are classes for virtual Directory and File implementations, Logger interfaces, Common exceptions... |
| Waarp ICAP Client | This module allows to add ICAP support for client side in Java. It is mainly intend to be used as a task in pre or post transfer using Waarp Gateway FTP or Waarp R66. |
| Waarp Compression | This module will support various compression model, to be used in "packet" (byte array) vision only. ZSTD is the first compression algorithm to be included, both for its efficiency and speed. |
| Waarp Exec | The Waarp Exec project is about a Daemon for local execution of system commands (as System.exec) but through client/server model and not within the same JVM. |
| Waarp Snmp | Waarp SNMP support through SNMP4J |
| Waarp Thrift | Waarp Thrift interface for R66 |
| Waarp Password Management GUI and Console | Waarp Password Management GUI and Console |
| Waarp Ftp | The Waarp FTP project is a proposal of a new fresh FTP server implementation, fully in Java according to the following RFC: RFC 959, RFC 775, RFC 2389, RFC 2428, RFC 3659. It includes also extra commands like XCRC, XMD5, XSHA1, INTERNALSHUTDOWN. It is based mainly on the NETTY framework (NIO great framework support) and is tend to be really efficient, both in term of memory, threads and network bandwidth. Bandwidth limitation can be configured both in store and retrieve, per session (although only one value is set by default, but it can be changed dynamically if needed) or globally to the server and of course with no limitation at all if wanted. Limitation should be enough to change the bandwidth behaviour for instance depending on the time in the day, so as to allow to limit bandwidth usage when users are at work and in contrary to allow more speed when only batchs are running. The specificity of this project is you can adapt this software to your particular needs by: changing the pre or post action on commands (not ony transfer), changing the underlying representation of files and directories (for instance with database entries), using any particular authentication mechanism. |
| Waarp Ftp R66 client | FTP client -wrapper of ftp4j- for Waarp solution |
| Waarp Gateway Kernel | Waarp Gateway contains the kernel for Http Gateway |
| Waarp OpenR66 | OpenR66 is a File Transfer Monitor to be used in real production to transfer files between servers. It allows to start/restart a transfer, check the remote MD5, check status, make pre or post actions on transfer, ... It includes Bandwidth limitation and will support SSL channel. When multiple transfers occurs between two hosts, they use the same network channel and multiplex their other transfers on this channel. |
| Waarp Gateway Ftp | Full Waarp FTP Server with Gateway support as Waarp Project: this is an extension of Waarp FTP server with execution support at the end of a transfer. |
| Waarp Proxy in R66 protocol | Waarp Proxy in R66 protocol |
| Waarp Http | This module allows to use HTTP transport for MFT, primarily from within a Web crawler for end users (JRE 8 end greater) |
| Waarp Extensions for JRE 8 and greater | Waarp S3 Client supports file, both as source or destination, for Waarp R66. Waarp Elasticsearch supports extends Exporter Monitor for Waarp R66. (JRE 8 and greater) |