Have you tried using an Ajax call to execute the ftp protocol using the
browser? The danger would be you'd expose the username/password of your
receiving FTP server, so you'd have to configure an account with put-only
privileges and some sort of receiving script.
You'll have a challenge with
>>>but actually HTTP needs to encode(base64) the binary content into plain
text and increases the total transfer size by ~1/3.
Actuully scratch that. I was thinking of something else. But I did have good
luck with the embedded FTP client. It worked very well. Especially for
failed uploads.
G!
>> The FTP protocol is intended for file transfers yes, but on single file
uploads I don;t imagine you will see a big difference.
One would think... but actually HTTP needs to encode(base64) the binary
content into plain text and increases the total transfer size by ~1/3. So
an 800 meg file will
big files are going to take a long time to upload, this is just a fact
of life i'm afraid. most peoples broadband speed has much slower
upstream than downstream, changing protocols is not going to suddenly
make things faster.
The FTP protocol is intended for file transfers yes, but on single
file
OK thanks. We were using the asfusion uploader and now started moving to the
cffileupload tag as well, but users are still complaining it is taking too long
to upload files (Some files are as big as 800mb).
> in order to FTP a file from the client machine you would need to be
> able to connec
in order to FTP a file from the client machine you would need to be
able to connect to the clients machine, which means they would need to
be running an FTP server, or you would need to run some kind of FTP
client on their machine to FTP the file to your server. Otherwise the
file needs to be on t
Does anyone know if it is possible to upload a file browsed by a user using
CFFTP instead of CFFILE "upload"? We are trying to find a solution which will
upload files faster than using CFFILE "upload". Any ideas?
~|
Order th
7 matches
Mail list logo
