Glossary |
 |
| 2-Tier Download | A FileUpEE 2-tier download is a download from a Web server to a file server. |
|---|---|
| 3-Tier Download | A FileUpEE 3-tier download is a download from a file server to a Web server to a browser. |
| 2-Tier Upload | A FileUpEE 2-tier upload is an upload from browser 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 browser to Web server to
file server. 3-tier uploading allows you to maintain a secure file server that
is isolated from your public Web server. 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, SoftArtisans XFile, or SoftArtisans JFile. |
| FileUp Standard Edition | Standard FileUp
 is
a server-side file transfer tool. Like FileUpEE, FileUp can perform
2-tier RFC 1867 uploads and secure downloads. Unlike FileUpEE,
Standard FileUp cannot perform 3-tier file transfers or process SOAP requests. FileUp
can upload up to 4 GB. If you have created upload applications using Standard FileUp, you can use FileUpEE to create 3-tier uploads (client -> Web Server -> file server) without rewriting your existing Standard FileUp scripts. FileUpEE's FileUpCompat property allows you to use FileUpEE with Standard FileUp. For more information on using the two products together, see Standard FileUp Support. Important: Standard FileUp and FileUpEE have different object models. To run a Standard FileUp script, you must install Standard FileUp. |
| ISAPI Filter | With FileUpEE's ISAPI filter, upload size is unlimited. 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's ISAPI filter is used under ASP.NET to overcome ASP.NET's inefficient memory utilization and to allow accurate progress indication. 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. |
| 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 a server-to-server upload that was suspended because of a network connection failure. In a resumable upload, if the upload from Web server to file server 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 in a form-based upload request
(RFC 1867), the XML payload can contain application logic and instructions to be executed
on the file server. 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 © 2003, SoftArtisans, Inc.