Deutsch   English   Français   Italiano  

View for Bookmarking (what is this?)
Look up another Usenet article

Path: ...!!!!!!not-for-mail
From: =?ISO-8859-15?Q?Andr=E9s_Garc=EDa?= <>
Newsgroups: comp.lang.tcl
Subject: Ann TclCurl 0.15.1
Date: Wed, 11 Jan 2006 00:36:05 +0100
Organization: Telefonica Data Espagna
Lines: 51
Message-ID: <dq1gkc$2c8$>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-15
Content-Transfer-Encoding: 8Bit
X-Trace: 1136936397 2440 (10 Jan 2006 23:39:57 GMT)
NNTP-Posting-Date: Tue, 10 Jan 2006 23:39:57 +0000 (UTC)
User-Agent: KNode/0.9.2



I have just released a new version of TclCurl updated for libcurl 7.14.1,
with TclCurl you can download and upload files using protocols like
ftp, tftp, http, https, ldap, telnet, dict, gopher and file.

The main changes since the last version are:

    * TFTP support.

    * New configure options:

        * ftpskippasvip: If set to a non-zero value, it instructs
          TclCurl not to use the IP address the server suggests
          in its 227-response to TclCurl's PASV command when TclCurl
          connects the data connection. Instead TclCurl will re-use
          the same IP address it already uses for the control
          connection. But it will use the port number from the

        * ftpfilemethod: It allows three values:

              * multicwd: the default, TclCurl will do a single CWD
                operation for each path part in the given URL. For
                deep hierarchies this means very many commands. This
                is how RFC1738 says it should be done.

              * nocwd: no CWD at all is done, TclCurl will do SIZE,
                RETR, STOR etc and give a full path to the server.

              * singlecwd: make one CWD with the full target directory
                and then operate on the file "normally".

          The support for this options is still experimental, comments
          whether the methods work or don't with different servers are

          Likewise, the options, or their names, may change in future
          releases, so they are not yet documented elsewhere.

     * Bug fix: The Windows packages had defective 'doc' directories,
       many thanks to Alex Hisen for letting me know.

For more information, please visit:

Share the wonders,