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.
Agreed. The concept is a bit confusing.  This is serving the purpose to signify if a header must be the next event or if a data or a header could be next.  If the later case holds then I need to be able to queue potential headers that may be received.  If a data frame is not acceptable next (1xx response received) then the Accumulator can stay in the state where headers have not been received.

One of the issues is that I have no trigger to indicate if the headers have been completely read.  Would you mind if I added the END_HEADERS indicator to the onHeadersRead method?  I would like to have a more definitive trigger to send headers up the pipeline.  I think this may help me to restructure, clarify, and perhaps generalize between the request/response flow a bit.