walkero
/
nghttp2
1
0
Fork 0
Code Issues Pull Requests Projects Releases 1 Wiki Activity

Update README.rst

This commit is contained in:
Tatsuhiro Tsujikawa 2013-07-17 00:08:05 +09:00
parent 76b430c26b
commit 18338199f5
1 changed files with 20 additions and 17 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

37
README.rst
View File

@ -7,21 +7,24 @@ version 2.0.
Development Status Development Status
------------------ ------------------
We started work based on spdylay codebase and just replaced spdylay We started to implement HTTP-defat-04/2.0
keyword with nghttp2. So just now it is just a relabled SPDY (http://tools.ietf.org/html/draft-ietf-httpbis-http2-04) based on
implementation and is not HTTP/2.0 implementation at all. To take spdylay code base.
advantage of the existing code, we will perform the following steps to
implement HTTP/2.0 based on implementation draft
(http://tools.ietf.org/html/draft-ietf-httpbis-http2-04):
1. Implement HTTP/2.0 frames and semantics, except for header The following features are not implemented:
compression. Server push may be omitted because I am not so
interested in it. * Header compression: currently, the library still uses SPDY/2 style
2. Modify spdycat and spdyd to work with new library code and perform header compression.
internal testing. We use NPN for TLS for now. * Header continuation: the library does not handle header continuation
3. Implement header compression, which may be based on draft-x (x >= and END_HEADERS flag has no meaning.
1). * Client connection header: spdycat and spdyd do not send/handle
4. Add new client and server which can perform HTTP upgrade mechanism. client connection header.
5. At this step, the library and demo client/server should be * ALPN: spdycat and spdyd use openssl without ALPN support and still
interoperable to the other implementation. Do some interoperable uses NPN to negotiate HTTP-draft-04/2.0.
testing with the other ones (e.g., node-http2)
With those missing parts, the library is still not inter-operable
right now.
The spdycat and spdyd are (the names are now odd for HTTP/2.0) working
now assuming the above limitation. You can see the HTTP/2.0 frames
back and forth and connection-level and stream level flow controls.