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.
The standardization process of QUIC has been taken to the IETF and can be followed on the IETF QUIC Mailing list. I'd like us to get on the bandwagon. Ideally, this would be done with a separate library/project to handle the binary/framing layer in a similar fashion to how HTTP/2 is implemented. This, to allow other projects to benefit from the work and to thus broaden the interest and chance of others to participate.
Two cookie drafts have been adopted by the httpwg in IETF and we should support them as the popular browsers will as well:
How to find services for specific domains/hosts.
Or perhaps even better: revamp the formpost API completely while we're at it and making something that is easier to use and understand:
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?