umgeher/cowboy
0
Fork 0
mirror of https://github.com/ninenines/cowboy.git synced 2025-07-14 12:20:24 +00:00
Code Issues Wiki Activity

Update ROADMAP

Browse source
This commit is contained in:
Loïc Hoguin 2013-05-24 14:59:30 +02:00
parent 22f961a7e8
commit 7eca879043
1 changed files with 18 additions and 37 deletions
Download patch file Download diff file Expand all files Collapse all files

55
ROADMAP.md
View file

@ -3,58 +3,39 @@ ROADMAP
This document explains in as much details as possible the This document explains in as much details as possible the
list of planned changes and work to be done on the Cowboy list of planned changes and work to be done on the Cowboy
server. It is non-exhaustive and subject to change. Items server. It is intended to be exhaustive but some elements
are not ordered. might still be missing.
* Add and improve examples All the following items must be done before Cowboy 1.0 is
released.
* Improve user guide * Parse support for all standard HTTP/1.1 headers
We need feedback to improve the guide. * Support for multipart requests and responses
* Add and improve tests * Convenience API for extracting query string and body
information, similar to PHP's $_GET, $_POST and $_FILES
Amongst the areas less tested there is protocol upgrades * Add Range support to REST
and the REST handler.
While eunit and ct tests are fine, some parts of the
code could benefit from PropEr tests.
* Continuous performance testing
Initially dubbed the Horse project, Cowboy could benefit
from a continuous performance testing tool that would
allow us to easily compare the impact of the changes we
are introducing, similar to what the Phoronix test suite
allows.
Depending on the test it may be interesting to compare
Cowboy to other servers and eventually take ideas from
the servers that outperform Cowboy for the task being tested.
* Full HTTP/1.1 support
* Improved HTTP/1.0 support
Most of the work on Cowboy has been done with HTTP/1.1
in mind. But there is still a need for HTTP/1.0 code in
Cowboy. The server code should be reviewed and tested
to ensure compatibility with remaining HTTP/1.0 products.
* Continue improving the REST API
* SPDY support * SPDY support
The following items pertain to Ranch. We are only interested in supporting existing
implementations, not the full protocol, as this
protocol has been abandoned in favor of HTTP/2.0
* Complete the user guide
The following items pertain to Ranch, but are equally important.
* Resizing the acceptor pool * Resizing the acceptor pool
We should be able to add more acceptors to a pool but also We should be able to add more acceptors to a pool but also
to remove some of them as needed. to remove some of them as needed
* Add Transport:secure/0 * Add Transport:secure/0
Currently Cowboy checks if a connection is secure by Currently Cowboy checks if a connection is secure by
checking if its name is 'ssl'. This isn't a very modular checking if its name is 'ssl'. This isn't a very modular
solution, adding an API function that returns whether solution, adding an API function that returns whether
a connection is secure would fix that issue. a connection is secure would fix that issue