csASPUpload 1.3

Chestysoft csASPUpload version 1.3

SINGLE SERVER LICENCE.

PLEASE READ THESE TERMS AND CONDITIONS BEFORE INSTALLING THE SOFTWARE.

These terms and conditions apply to the Chestysoft csASPUpload programme and any accompanying documentation (referred to as "the software"). By installing the software, you are considered to have agreed to the terms and conditions.

This licence grants you a non-exclusive licence to install and use the

Chestysoft csASPUpload version 1.3

SINGLE SERVER LICENCE.

PLEASE READ THESE TERMS AND CONDITIONS BEFORE INSTALLING THE SOFTWARE.

These terms and conditions apply to the Chestysoft csASPUpload programme and any accompanying documentation (referred to as "the software"). By installing the software, you are considered to have agreed to the terms and conditions.

This licence grants you a non-exclusive licence to install and use the

software on a single server computer. You may transfer the software to

another computer only if you delete the previous installation.

In addition it allows you to install and use one copy of the

software on a single non-server computer.

The software is the intellectual property of Chestysoft, and may not

be copied except for backup purposes and for installation as described

above. You may not resell or otherwise distribute the software.

The software is sold "as is" and without warranties as to performance

or purpose. Any liability of Chestysoft will be limited to product

replacement or refund of the purchase price.

Chestysoft, November 2003.

Web site: www.chestysoft.com

Email: info@chestysoft.com

kitster 2006-11-16 08:44:08

Lacking documentation, file size limit

I was looking forward to a cheap, quality component. But, you get what you pay for. There is a file size cap. But, no-one knows what it is. I was trying to upload 400MB+ files, and it failed, very unhelpfully. Simon Chester replied to all my emails with pretty much the same workaround, don't upload files that big. There is no mention of file size or format limitations within the products documentation, so I thought I should post this email from him to me explaining this point:
---------------------------------------
The workaround is to not upload 750 MB files using an HTTP post. It is possible with some components, but not ours. Our component holds the entire upload in memory as it processes it, and this is very demanding on memory when very large files are uploaded. We have a reason for doing it this way because it is often used with images and there advantages in being able to process an image without saving it to disk first. An alternative method of processing the upload would be to write it to disk as it uploads and this would reduce the memory requirements. This method has many disadvantages and it would not be a good way of dealing with smaller files.

Even if you have a component that can save the file I would not recommend uploading files of this size using this method. FTP would be a more appropriate method of transferring files of this size.
--------------------------------------------------
If you require a professional upload component, look elsewhere. Home bloggers, simple users, probably not a problem. But be aware. Well over 2 days of my own time worth of investigation, and then another component to replace Chesty's. Not recommended.