JFileUpload is a Java applet that allows you to upload files and folders to any Web or FTP server. It can be integrated into any application. The server-side technology could be JSP/Servlet, PHP, Coldfusion, CGI, or Microsoft ASP. The front-end provides an upload progress bar, a cancel button, and drag and drop support.
JFileUpload is a Java applet that allows uploading of files and folders to any Web or FTP server. This component can be integrated into any application, whether the server-side technology is JSP/Servlet, PHP, Coldfusion, CGI, or Microsoft ASP. The front-end provides an upload progress bar, a cancel button, and drag-and-drop support. JFileUpload supports very large uploads over 2GB and can resume broken uploads. Its colors, size, and language can be customized.
Serv-U is a powerful and easy-to-use file server which supports the FTP, HTTP, and SFTP (via SSH2) protocols to ensure maximum compatibility with the widest range of transfer client software. It supports SSL encryption, provides a Web-based interface to allow administrators to remotely access and configure the file server, includes a built-in transfer client to allow users to upload and download files from their Web browsers, provides photo sharing capabilities, integrates with Active Directory (providing levels of security based on Organizational Units), and can be accessed and administered in 13 different languages simply by choosing an appropriate language upon login.
WAWAS is a full PHP application server. The main server core listens to any IP/port and passes data to any mounted protocol on the listener. Implemented protocols are HTTP1.1/1.0, Comet, Telnet, DNS, mail, and FTP. Each protocol runs modules that build response data based on the requests. Memory object persistence allows data and caches to be shared across protocols or time. All configuration uses XML. It can be launched as a daemon, with or without forked workers, and is nearly as fast as Apache in preliminary tests.
Universal File Mover (UFM) manages the transfer of files. The user combines a series of Action commands to create the UFM Workflow XML file. These Action commands define which actions are to be taken, the order of the actions, and how errors are to be handled. UFM processes the Action commands as per the UFM Workflow XML file. UFM currently contains 41 Action commands. These action commands fall into five categories: WebSphere MQ Actions, Network Actions, File Actions, Control Actions, and Other Actions. UFM can transfer files in one of five ways, using WebSphere MQ, FTP, SFTP, SCP, or HTTP.