Re: Large/unreliable file uploading over HTTP
| From: | mike | Date: | Mon, 08 Sep 2008 21:10:05 +0000 |
| Subject: | Re: Large/unreliable file uploading over HTTP | ||
| References: | 1 2 3 4 5 6 7 8 9 | Groups: | php.general |
| Request: | Send a blank email to php-general+get-279700@lists.php.net to get a copy of this message | ||
On Mon, Sep 8, 2008 at 2:00 PM, Boyd, Todd M. <tmboyd1@ccis.edu> wrote:
> I know that Base64 encoding adds something like 30% to the overall volume of the object once it
> has been encoded. For huge files, that might be unacceptable. I'm not sure how UUEncode handles
> it.
yeah, I found an email thread from 2001 saying base64 is the way to
go. however for every 6 bytes it creates 8 bytes or something (hence
the 33% bloat)
there's also options like http://www.yenc.org/ - but this
would
require java support (or appropriate extensions written) and
server-end support (PHP, or in-webserver code)
base64 is -probably- the easiest. PHP has both uuencode and base64
standard. However, need to look at it from the client angle - Java
probably has base64 easily available, not sure about uudecode. Not
sure about flash, or any other client programs; or web browsers
themselves too...