TODO: Fixed some spelling mistakes

 1.4 signal-based resolver timeouts

 1.5 get rid of PATH_MAX

 1.6 Modified buffer size approach

 1.7 Detect when called from witin callbacks

 1.7 Detect when called from within callbacks

 1.8 Allow SSL (HTTPS) to proxy

 2. libcurl - multi interface

 2.2 Fix HTTP Pipelining for PUT

 3. Documentation

 3.1 Update date and version in man paegs

 3.1 Update date and version in man pages

 4. FTP

 4.1 HOST

 17.5 Add support for concurrent connections

 18. Next SONAME bump

 18.1 http-style HEAD output for ftp

 18.1 http-style HEAD output for FTP

 18.2 combine error codes

 18.3 extend CURLOPT_SOCKOPTFUNCTION prototype

 Dynamically allocate buffer size depending on protocol in use in combination

 with freeing it after each individual transfer? Other suggestions?

1.7 Detect when called from witin callbacks

1.7 Detect when called from within callbacks

 We should set a state variable before calling callbacks, so that we

 subsequently can add code within libcurl that returns error if called within

4.3 Earlier bad letter detection

 Make the detection of (bad) %0d and %0a codes in FTP url parts earlier in the

 Make the detection of (bad) %0d and %0a codes in FTP URL parts earlier in the

 process to avoid doing a resolve and connect in vain.

4.4 REST for large files

 For example:

 http://test:pass;auth=NTLM@example.com would be equivalent to specifing --user

 http://test:pass;auth=NTLM@example.com would be equivalent to specifying --user

 test:pass;auth=NTLM or --user test:pass --ntlm from the command line. 

 Additionally this should be implemented for proxy base URLs as well.

 Currently the LDAP module only supports ldap_simple_bind_s() in order to bind

 to an LDAP server. However, this function sends username and password details

 using the simple authentication mechanism (as clear text). However, it should

 be possible to use ldap_bind_s() instead specifing the security context

 be possible to use ldap_bind_s() instead specifying the security context

 information ourselves.

11. New protocols

12.4 Cache OpenSSL contexts

 "Look at SSL cafile - quick traces look to me like these are done on every

 request as well, when they should only be necessary once per ssl context (or

 request as well, when they should only be necessary once per SSL context (or

 once per handle)". The major improvement we can rather easily do is to make

 sure we don't create and kill a new SSL "context" for every request, but

 instead make one for every connection and re-use that SSL context in the same

17.3 more protocols supported

 Extend the test suite to include more protocols. The telnet could just do ftp

 Extend the test suite to include more protocols. The telnet could just do FTP

 or http operations (for which we have test servers).

17.4 more platforms supported

18. Next SONAME bump

18.1 http-style HEAD output for ftp

18.1 http-style HEAD output for FTP

 #undef CURL_FTP_HTTPSTYLE_HEAD in lib/ftp.c to remove the HTTP-style headers

 from being output in NOBODY requests over ftp

 from being output in NOBODY requests over FTP

18.2 combine error codes

 but instead often restricts how the form functions can or can't be modified.

 Changing them to return a private handle will benefit the implementation and

 allow us much greater freedoms while still maintining a solid API and ABI.

 allow us much greater freedoms while still maintaining a solid API and ABI.

19.9 have form functions use CURL handle argument

 Rather than use the URL to specify the mail client string to present in the

 HELO and EHLO commands, libcurl should support a new CURLOPT specifically for

 specifing this data as the URL is non-standard and to be honest a bit of a

 specifying this data as the URL is non-standard and to be honest a bit of a

 hack ;-)

 Please see the following thread for more information: