Upgrading to HTTP/2 draft 14 HTTP/1.x message flow

Motivation:

HTTP/2 draft 14 came out a couple of weeks ago and we need to keep up
with the spec.

Modifications:

-Allow informational type messages to be sent up the pipeline immediatley.
-Corrections to HttpObject comparitors to support test cases
-New test cases to support sending headers immediatley
-Bug fixes cleaned up to ensure the message flow is terminated properly

Result:
Netty HTTP/2 to HTTP/1.x translation layer will support the HTTP/2 draft message flow.
>Will it always be the case that for a server the message is a request and for a client the message is a response?

Yes. The following section clarifies http://tools.ietf.org/html/draft-ietf-httpbis-http2-14#section-8.1.

>What about push promises? Or can we simply not accept push promises?

I believe push promises can be accepted as responses (only server is allowed to do push promise).  The corresponding headers will just be queued along with the typical message flow.  Is there something specific you had in mind that might cause an issue?