Re: Http put Vs ftp

FTP stands for File Transfer Protocol, and is one of the old-timey ways to
shunt files around the internet.  FTP relies on having an FTP daemon set up
on whatever machine is the host machine that you're pushing files to.  FTP
itself is notoriously insecure.  SFTP (FTP over SSH) is an unrelated
implementation with a similar interface to FTP made subsequently to address
FTP's total lack of security.

HTTP PUT is a RESTful HTTP verb, along side other verbs like GET, POST,
DELETE and HEAD.  The intention for PUT is to update an existing resource
(which is denoted by some URI, such as http://example.host.net/video/1.html)
with new data sent in HTTP headers (just as what happens when you POST to a
resource).  POSTs like any HTTP verb can be performed over secure
connections using SSH and a browser's builtin facility for negotiating https
connections signed with security certificates.

If your goal is to set up a personal server to upload files to and from, you
want to use something like FTP.

If your goal is to accept, and update content from users (who may be
untrusted -- and you should always assume your users are untrusted), then
you probably want a web app that uses things like POST and PUT to receive
data and files.

Fundamentally, FTP and HTTP do very different things and aren't really
directly comparable.  To give you a more useful example, i would have to
know more about what it is that you're atually trying to accomplish.

-Ted

On Tue, Feb 22, 2011 at 5:08 AM, Datta321 <DS0036943@techmahindra.com>wrote:

> Can anyone explain in detail the *difference* between *Http PUT *and* FTP
> *with an example ?
> ------------------------------
> View this message in context: Http put Vs ftp<http://old.nabble.com/Http-put-Vs-ftp-tp30984384p30984384.html>
> Sent from the w3.org - www-smil mailing list archive<http://old.nabble.com/w3.org---www-smil-f11729.html>at Nabble.com.
>