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
|
|
|
|
2014-06-10 12:00:30 +02:00
|
|
|
1.0 (R16 and R17)
|
|
|
|
|
-----------------
|
2012-02-27 09:54:16 +01:00
|
|
|
|
2014-06-10 12:00:30 +02:00
|
|
|
We are now in the final push to Cowboy 1.0. Further changes
|
|
|
|
|
are expected to be bug fixes and documentation improvements.
|
2012-02-27 09:54:16 +01:00
|
|
|
|
2014-06-10 12:00:30 +02:00
|
|
|
2.0 (R17 and R18)
|
|
|
|
|
-----------------
|
2012-02-27 09:54:16 +01:00
|
|
|
|
2014-06-10 12:00:30 +02:00
|
|
|
* HTTP/2.0
|
2012-02-27 09:54:16 +01:00
|
|
|
|
2014-06-10 12:00:30 +02:00
|
|
|
* Websocket permessage deflate compression
|
2012-02-27 09:54:16 +01:00
|
|
|
|
2014-06-10 12:00:30 +02:00
|
|
|
* Better cowboy_req usability
|
2012-02-27 09:54:16 +01:00
|
|
|
|
2014-06-10 12:00:30 +02:00
|
|
|
The number one usability concern with Cowboy today is
|
|
|
|
|
the need to keep the Req object. Most functions in
|
|
|
|
|
cowboy_req don't actually modify it and probably never
|
|
|
|
|
will. This change will make sure that only the required
|
|
|
|
|
function return a new Req.
|
2013-09-18 20:29:01 +02:00
|
|
|
|
2014-06-10 12:00:30 +02:00
|
|
|
At the same time, some of the functions that cache their
|
|
|
|
|
results will stop to do so. This will save memory and
|
|
|
|
|
allow us to not modify the Req.
|
2013-09-18 20:29:01 +02:00
|
|
|
|
2014-06-10 12:00:30 +02:00
|
|
|
* Start experimenting with maps.
|
2013-11-14 15:34:16 +01:00
|
|
|
|
|
|
|
|
Under consideration
|
|
|
|
|
-------------------
|
|
|
|
|
|
|
|
|
|
* Convenience API for extracting query string and body
|
|
|
|
|
information, similar to PHP's $_GET, $_POST and $_FILES
|
