linux-c-programming.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: Vger Kernel <linux-c-programming@vger.kernel.org>
Subject: Re: what is libcurl
Date: Fri, 26 Nov 2004 21:30:40 +0100	[thread overview]
Message-ID: <20041126203040.GZ2067@lug-owl.de> (raw)
In-Reply-To: <20041126090510.860.qmail@web53008.mail.yahoo.com>

[-- Attachment #1: Type: text/plain, Size: 1194 bytes --]

On Fri, 2004-11-26 01:05:10 -0800, rinku rathore <rinku_ques@yahoo.com>
wrote in message <20041126090510.860.qmail@web53008.mail.yahoo.com>:
>  Hello,
> > Can you give me some more information about this
> > libcurl
> I wanted to ftp through C program without user
> intervention,Is this libcurl help if yes in what way.

I am not sure if libcurl implements all features FTP offers (eg.
password-authenticated upload, FTP with TLS/SSL, ...), but a good
starting point is probably libcurl's documentation that comes with the
sources.

libcurl's homepage is at http://curl.haxx.se/ ,  which is also the first
match for a Google search for "libcurl". The features libcurl offers
(http://curl.haxx.se/docs/features.html ,  linked from libcurl's home
page mentioned above) sound quite promising (for your application as
described by you).

MfG, JBG

-- 
Jan-Benedict Glaw       jbglaw@lug-owl.de    . +49-172-7608481             _ O _
"Eine Freie Meinung in  einem Freien Kopf    | Gegen Zensur | Gegen Krieg  _ _ O
 fuer einen Freien Staat voll Freier Bürger" | im Internet! |   im Irak!   O O O
ret = do_actions((curr | FREE_SPEECH) & ~(NEW_COPYRIGHT_LAW | DRM | TCPA));

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

      reply	other threads:[~2004-11-26 20:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-26  9:05 what is libcurl rinku rathore
2004-11-26 20:30 ` Jan-Benedict Glaw [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20041126203040.GZ2067@lug-owl.de \
    --to=jbglaw@lug-owl.de \
    --cc=linux-c-programming@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).