This commit is contained in:
Daniel Stenberg 2003-10-17 12:37:15 +00:00
parent 18b809e7e4
commit d095b20d1c
1 changed files with 6 additions and 12 deletions

View File

@ -80,8 +80,8 @@ TODO
HTTP HTTP
* Digest, NTLM and GSS-Negotiate support for HTTP proxies. They all work * Digest and GSS-Negotiate support for HTTP proxies. They only work on
on direct-connections to the server. direct-connections to the server.
* Pipelining. Sending multiple requests before the previous one(s) are done. * Pipelining. Sending multiple requests before the previous one(s) are done.
This could possibly be implemented using the multi interface to queue This could possibly be implemented using the multi interface to queue
@ -89,8 +89,6 @@ TODO
TELNET TELNET
* Make TELNET work on windows98!
* Reading input (to send to the remote server) on stdin is a crappy solution * Reading input (to send to the remote server) on stdin is a crappy solution
for library purposes. We need to invent a good way for the application to for library purposes. We need to invent a good way for the application to
be able to provide the data to send. be able to provide the data to send.
@ -143,14 +141,10 @@ TODO
* "curl ftp://site.com/*.txt" * "curl ftp://site.com/*.txt"
* Several URLs can be specified to get downloaded. We should be able to use * The client could be told to use maximum N simultaneous transfers and then
the same syntax to specify several files to get uploaded (using the same just make sure that happens. It should of course not make more than one
persistant connection), using -T. connection to the same remote host. This would require the client to use
the multi interface.
* When the multi interface has been implemented and proved to work, the
client could be told to use maximum N simultaneous transfers and then just
make sure that happens. It should of course not make more than one
connection to the same remote host.
* Extending the capabilities of the multipart formposting. How about leaving * Extending the capabilities of the multipart formposting. How about leaving
the ';type=foo' syntax as it is and adding an extra tag (headers) which the ';type=foo' syntax as it is and adding an extra tag (headers) which