Uploading from the middle of nowhere

We are an international NGO and sometimes people need to upload relatively large video/image files from an emergency site where internet is intermittent and weak.

To date, we have been using either FTP or HTTP (to upload to a hosted image database), but both fail more often than they succeed, which exasperates staff.

I understand that the Bittorrent protocol breaks files into chunks and sends them bit by bit, and thus might be more resilient to intermittent connections.  Is this the best thing for me to look into, or are there other solutions that would be more promising?

Anyone have any links that might help, please?
concern_supportAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

owner66Commented:
Without knowing too much about your client/server operating systems, etc., i do know that Filezilla client supports resume of upload.

"Step 6. If the FTP connection is broken before finishing the file upload, rather than uploading the whole file again, FileZilla allows you to resume uploading from the last broken point. To resume the uploading, just try to upload the file again and choose the "Resume" option in the pop up window."

I would experiment with that first.
Filezilla is not the only one that provides this, but it works great.

0
AlexPaceCommented:
FTP resume should work for you but it requires that the sever to support the REST raw FTP command.

You may also want to check that both your FTP client and server support MODE Z for on-the-fly zip compression and experiment with different compression levels to see if you can reduce transfer time that way.
0
concern_supportAuthor Commented:
Thanks guys.

I'm not sure if my ftp server supports the REST raw command. How could I tell?  

(It's a SBS 03 sever and I've googled for terms like "sbs 03 rest ftp support"), but can't find anything to learn from.
0
AlexPaceCommented:
You could use an FTP client that can send a raw command and either display the protocol trace (or create a log file containing it.)

Then send "REST 1000" and, if the server supports it, you'll see a three digit response code like:
"350 Restarting at 1000. Send STOR or RETR to initiate transfer"

If the three digit response code starts with a 4 or a 5 that means the server can't do it.

Another less direct way to find out is to send a raw FEAT to request a list of the "features" supported by the server... just check to see if REST and MODE Z are in the server's response to FEAT.  Some clients send FEAT automatically when they first log in so you might not even have to figure out how to send manual commands as long as you have a good protocol-level log file.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
concern_supportAuthor Commented:
Apolgies for abandoning this question, the notification of new replies was going to the wrong email address.  I'll look into what you have suggested.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Networking

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.