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.
@Scottmitch I could be missing your point here, apologies if that's the case...

I would expect #1 to be the main mode of operation for HTTP applications and I would expect it to be the only mode supported by this class.

If an application wanted #2, I would expect that they would just hook into the HTTP/2 layer rather directly (i.e. feed off of DelegatingHttp2ConnectionHandler via the Http2FrameObserver interface ... in the same way that this class gets events) rather than expanding the role of this class to support HTTP/2-aware applications. There are plenty of access points already for getting notified of HTTP/2 events. Do you have a use case in mind where this wouldn't be sufficient, or would make building an application difficult?