This is a nice start. I considered implementing SPDY myself soon after the
spec was first published but the TLS stuff seemed too daunting. At the time
I think Chrome was using a bunch of in-tree OpenSSL patches to support
next-protocol-negotiation / TLS snap start / etc. It looks like the HTTP 2
draft has gotten rid of those requirements but the TLS server name
indication extension must be supported. HsOpenSSL doesn't have bindings for
the needed functions (SSL_CTX_set_tlsext_servername_callback() /
SSL_get_servername()) and the tls library (which I am personally reluctant
to use for "crypto is hard to do right and you really want to use
widely-audited code" reasons) doesn't seem to have an implementation yet
either. OpenSSL support seems to be the easier nut to crack there.
On Mon, Dec 16, 2013 at 9:03 PM, Kazu Yamamoto
Hi guys,
I would like to announce the first release of the http2 package.
http://hackage.haskell.org/package/http2
This package tries to implement the coming HTTP/2.0. HTTP/2.0 is being standardized in two internet-drafts:
http://tools.ietf.org/html/draft-ietf-httpbis-http2-09
http://tools.ietf.org/html/draft-ietf-httpbis-header-compression-05
The current version of the http2 library implements the latter (called HPACK) only at this moment.
I would like to make this library so that other HTTP libraries can use when supporting HTTP/2.0. Feedback is welcome.
--Kazu _______________________________________________ web-devel mailing list web-devel@haskell.org http://www.haskell.org/mailman/listinfo/web-devel
--
Gregory Collins