PUT is better in that the zipped files are sent in their original
form, much like they would be using FTP. POSTing always converts
the data to some mimetype of "multipart/urlencoded" or something
like that, which also in effect encodes the file from binary
to an ascii encoding like uuencode or base64, thus making the
actual transferred data larger, and I consider this to also be
more taxing on the server, especially with larger files. I also
am not sure if POSTing can be resumed like PUT's can be now.

But if you are only dealing with small files, POSTing should be
OK, although I'm not sure why you would want to use curl for that,
unless you are trying to automate something, because you can
typically do posting directly from a web form.

Bob Schader

pit_at_paradise.net.nz wrote:
>
> Thank you for the reply.
>
> But i couldn't help myself asking this question.
>
> "What is the advantage of doing PUT, instead of POST ?"
>
> To me, it seems easier to do POST than doing PUT.
>
> Can you recommend any articles or doc for me?
>
> All i need to do is moving some zipped files over http.
> (The server will store the files for only a short time)
> And authenticate with user name and password.
>
> _______________________________________________
> Curl-library mailing list
> Curl-library_at_lists.sourceforge.net
> http://lists.sourceforge.net/lists/listinfo/curl-library

_______________________________________________
Curl-library mailing list
Curl-library_at_lists.sourceforge.net
http://lists.sourceforge.net/lists/listinfo/curl-library
Received on 2001-02-03