 Enterprise Edition |
|
Glossary
| 2-Tier Download | A FileUpEE 2-tier download is a download from a Web server to a client. |
|---|---|
| 3-Tier Download | A FileUpEE 3-tier download is a download from a file server to a Web server to a client. |
| 2-Tier Upload | A FileUpEE 2-tier upload is an upload from client to Web server. FileUpEE handles 2-tier uploads according to the protocol for form-based file uploads defined in RFC 1867. |
| 3-Tier Upload | A FileUpEE 3-tier upload is an upload from client to Web server to
file server. 3-tier uploading allows you to maintain a secure file server that
is isolated from the Internet. FileUpEE handles the browser to server part of the upload according to the protocol for form-based file uploads defined in RFC 1867. FileUpEE can handle the server to server part of the upload as either an RFC 1867 request or as a SOAP request with an attachment. |
| FileUp Enterprise Developer Edition | FileUpEE Developer offers the same functionality as FileUpEE, but processes only one upload or one download at a time, which is the typical development environment. Other restrictions may apply. Licensing of FileUpEE Developer is per development server (not per developer). A developer license is required for every development server where FileUpEE Developer is installed. The developer license does not allow redistribution of FileUpEE Developer or SoftArtisans XFileEE. |
| FileUp Standard Edition | FileUp Standard Edition
 (FileUpSE) is
a server-side file transfer tool. Like FileUpEE, FileUpSE can perform
2-tier form-based file uploads (RFC 1867) and secure downloads.
Unlike FileUpEE, FileUpSE cannot perform 3-tier file
transfers or process SOAP requests. FileUp can upload up to 4-GB. If you have created upload applications using FileUpSE, you can use FileUpEE to create 3-tier uploads (client -> web Server -> file server) without rewriting your existing FileUpSE scripts. FileUpEE's FileUpCompat
property allows you to use FileUpEE with FileUpSE. For more information on using the two
products together, see
FileUpSE Support.Important: FileUpSE and FileUpEE have different object models. To run a FileUpSE script, you must install FileUpSE. |
| HttpModule | FileUpEE's HttpModule is an interceptor that is used under
ASP.NET to overcome inefficient memory utilization in ASP.NET and in IIS 6, to allow
accurate progress indication, and to allow uploads of greater than 4-GB.
The HttpModule intercepts an upload request, reads all the data,
and writes it to a temp file chunk by chunk, before sending it to ASP.NET.
With the HttpModule and
chunked transfer-encoding, upload size in IIS 6 is unlimited. Note that most browsers support uploads of up to 2 GB. Larger uploads must be generated by a client-side control that can handle very large transfers. FileUpEE includes SoftArtisans XFileEE, a client-side file transfer control that can submit uploads of any size. For performance reasons, the HttpModule will not intercept all ASP.NET requests. Only requests for files with the extension .uplx will be handled by the HttpModule. Requests for files with the extension .aspx will not be processed by the HttpModule; they will be sent directly to ASP.NET. This prevents burdening the server with unnecessary use of the HttpModule. |
| ISAPI Filter | FileUpEE's ISAPI filter is used in IIS 5 under ASP.NET to overcome ASP.NET's
inefficient memory utilization and to allow accurate progress indication.
Without the ISAPI filter, ASP.NET cannot handle very large uploads.
With the ISAPI filter, upload size in ASP.NET is unlimited.
The filter also significantly improves the performance of large uploads in
ASP. The ISAPI filter intercepts an upload request, reads all the data, and writes it to a temp file chunk by chunk,
before sending it to ASP or ASP.NET. Note that most browsers support uploads of up to 2 GB. Larger uploads must be generated by a client-side control that can handle very large transfers. FileUpEE includes SoftArtisans XFileEE, a client-side file transfer control that can submit uploads of any size. For performance reasons, the ISAPI filter will not intercept all ASP and ASP.NET requests. Only requests for files with the extensions .upl (for ASP) and .uplx (for ASP.NET) will be handled by the filter. Requests for files with the extensions .asp and .aspx will not be processed by the filter; they will be sent directly to ASP or ASP.NET. This prevents burdening the server with unnecessary use of the ISAPI filter. The ISAPI filter works in IIS 5, and in IIS 6 running in IIS 5 mode. If IIS 6 is running in IIS 6 mode, use the HttpModule. |
| Progress Indicator | FileUpEE includes a server-side progress indicator that allows you to log
and display the progress of an upload. The progress indicator monitors the whole
upload; it does not watch the progress of an individual file within an upload. FileUpEE's progress indicator can monitor uploads from client to web server, and from web server to file server. The progress from client to web server is measured as the number of bytes received on the web server. Progress from web server to file server is measured as the number of bytes sent from the web server; note that this is not proof of arrival on the file server. For more information on using the progress indicator, see The Progress Indicator. |
| Resumable Upload | FileUpEE can resume client-to-server and server-to-server uploads that were suspended because of a network connection failure. In a resumable upload, if the upload is suspended, and the user clicks a Resume link or button, FileUpEE gets the status of the upload from a database and resumes the upload from the point at which it stopped. For more information, see A Resumable Upload. |
| RFC 1867 |
RFC 1867
defines a protocol for
form-based file uploads. This type of upload submits form data
(the file and/or other form elements) as name/value pairs. FileUpEE handles
all uploads from browser to web server according to RFC 1867.
FileUpEE usually handles uploads from web server to file server as SOAP messages
with attachments, but can process server to server uploads according to RFC 1867
as in the example
3 Tier Upload with Standard FileUp. |
| SOAP Message with an Attachment |
In most cases, FileUpEE submits the server-to-server part of a file transfer as a
SOAP
message with an attachment. SOAP (Simple Object Access Protocol) is an Internet protocol
that uses HTTP as its transport and XML as its data format. A SOAP request is submitted
in an XML document (the XML payload) via HTTP. Unlike a form-based upload request
(RFC 1867), the XML payload can contain structured, hierarchical data. A server-to-server file transfer SOAP request contains the the SOAP message in XML format and one or more files as attachments. The MIME content-type of a SOAP message with an attachment is "multipart/related." The various parts of the request - the SOAP message and the file or files to upload - are separated by MIME boundaries. Each MIME part includes a Content-Type header that describes the embedded data (the SOAP message or a file to upload), and other header information. All the MIME parts - the SOAP message and the attached files - form the request's HTTP body. With FileUpEE, the server-to-server part of an upload or download is a SOAP request in all but two cases:
|
Copyright © 2005, SoftArtisans, Inc.