Here's an interesting request. A client will need to blog from the north pole. Their connection speed on their Satellite phone is really poor, so everything needs to be as lean as possible.
In the past, they've submitted text via a HTML form over HTTP, and FTP'd the images.
Anecdotally, from he comfort of my desk with a high speed broadband connection, It feels like HTTP is much faster for uploading files, compared to FTP. But I'm just a coder, I know nothing of the underlying technology that get's data from one part of the web to another so I thought it best to double check with people who tend to know a lot more about these things
I suppose the issues are: Bandwidth, & Reliability.
So, given these very strict conditions
Should they use FTP or HTTP to upload images from the North Pole?
Definitely HTTP if the client and server support partial upload. The reason is that FTP is a command-response protocol and with lousy connection it's quite easy to lose it even before it gets to uploading the file. Next, FTP requires two socket connections which is additional network load (and possible weak place in case of non-stable connection).
The question becomes more complicated if you can't provide partial upload capability (i.e. if the upload of the file fails, the file is re-uploaded completely). Then you need to decide, if connection is more slow or more unreliable (i.e. lost frequently), i.e. whether the chance of connection drop is higher than the overhead of FTP's secondary connection.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With