Roadmap of things Daniel Stenberg and Steve Holme want to work on next. It is intended to serve as a guideline for others for information, feedback and possible participation.
test suite
Base this on existing nghttp2 server to start with to make functional tests. Later on we can adopt that code or work with nghttp2 to provide ways to have the http2 server respond with broken responses to make sure we deal with that nicely as well.
To decide: if we need to bundle parts of the nghttp2 stuff that probably won't be shipped by many distros.
provide option for HTTP/2 “prior knowledge” over clear text
As it would avoid the roundtrip-heavy Upgrade: procedures when you know it speaks HTTP/2.
How to find services for specific domains/hosts.
To avoid network traffic to/from the proxy getting snooped on.
make sure there's an easy handle passed in to curl_formadd(), curl_formget() and curl_formfree() by adding replacement functions and deprecating the old ones to allow custom mallocs and more
add support for third-party SASL libraries such as Cyrus SASL - may need to move existing native and SSPI based authentication into vsasl folder after reworking HTTP and SASL code
...
Simplify the SMTP email interface so that programmers don't have to construct the body of an email that contains all the headers, alternative content, images and attachments - maintain raw interface so that programmers that want to do this can
Allow the email protocols to return the capabilities before authenticating. This will allow an application to decide on the best authentication mechanism
Allow Windows threading model to be replaced by Win32 pthreads port
Implement a dynamic buffer size to allow SFTP to use much larger buffers and possibly allow the size to be customizable by applications. Use less memory when handles are not in use?
Embed a language interpreter (lua?). For that middle ground where curl isn’t enough and a libcurl binding feels “too much”. Build-time conditional of course.
Simplify the SMTP command line so that the headers and multi-part content don't have to be constructed before calling curl
build for windows (considered hard by many users)
curl -h output (considered overwhelming to users)
we have > 170 command line options, is there a way to redo things to simplify or improve the situation as we are likely to keep adding features/options in the future too
docs (considered “bad” by users but how do we make it better?)
authentication framework (consider merging HTTP and SASL authentication to give one API for protocols to call)
Perform some of the clean up from the TODO document, removing old definitions and such like that are currently earmarked to be removed years ago