2012-02-27 09:54:16 +01:00
|
|
|
ROADMAP
|
|
|
|
=======
|
|
|
|
|
|
|
|
This document explains in as much details as possible the
|
|
|
|
list of planned changes and work to be done on the Cowboy
|
2013-05-24 14:59:30 +02:00
|
|
|
server. It is intended to be exhaustive but some elements
|
|
|
|
might still be missing.
|
2012-02-27 09:54:16 +01:00
|
|
|
|
2013-05-24 14:59:30 +02:00
|
|
|
All the following items must be done before Cowboy 1.0 is
|
|
|
|
released.
|
2012-02-27 09:54:16 +01:00
|
|
|
|
2013-05-24 14:59:30 +02:00
|
|
|
* Parse support for all standard HTTP/1.1 headers
|
2012-02-27 09:54:16 +01:00
|
|
|
|
2013-05-24 14:59:30 +02:00
|
|
|
* Support for multipart requests and responses
|
2012-02-27 09:54:16 +01:00
|
|
|
|
2013-05-24 14:59:30 +02:00
|
|
|
* Convenience API for extracting query string and body
|
|
|
|
information, similar to PHP's $_GET, $_POST and $_FILES
|
2012-02-27 09:54:16 +01:00
|
|
|
|
2013-05-24 14:59:30 +02:00
|
|
|
* Add Range support to REST
|
2012-02-27 09:54:16 +01:00
|
|
|
|
2013-05-24 14:59:30 +02:00
|
|
|
* SPDY support
|
2012-02-27 09:54:16 +01:00
|
|
|
|
2013-05-24 14:59:30 +02:00
|
|
|
We are only interested in supporting existing
|
|
|
|
implementations, not the full protocol, as this
|
|
|
|
protocol has been abandoned in favor of HTTP/2.0
|
2013-02-11 09:37:55 +01:00
|
|
|
|
2013-05-24 14:59:30 +02:00
|
|
|
* Complete the user guide
|
2012-02-27 09:54:16 +01:00
|
|
|
|
2013-05-24 14:59:30 +02:00
|
|
|
The following items pertain to Ranch, but are equally important.
|
2012-02-27 09:54:16 +01:00
|
|
|
|
2013-01-29 01:19:49 +01:00
|
|
|
* Resizing the acceptor pool
|
2012-02-27 09:54:16 +01:00
|
|
|
|
|
|
|
We should be able to add more acceptors to a pool but also
|
2013-05-24 14:59:30 +02:00
|
|
|
to remove some of them as needed
|
2012-02-27 09:54:16 +01:00
|
|
|
|
2013-01-29 01:19:49 +01:00
|
|
|
* Add Transport:secure/0
|
2012-02-27 09:54:16 +01:00
|
|
|
|
|
|
|
Currently Cowboy checks if a connection is secure by
|
|
|
|
checking if its name is 'ssl'. This isn't a very modular
|
|
|
|
solution, adding an API function that returns whether
|
2013-05-24 14:59:30 +02:00
|
|
|
a connection is secure would fix that issue
|