HTTP/2 to HTTP priority translation

Motivation:

The priority information reported by the HTTP/2 to HTTP tranlsation layer is not correct in all situations.
The HTTP translation layer is not using the Http2Connection.Listener interface to track tree restructures.
This incorrect information is being sent up to clients and is misleading.

Modifications:
-Restructure InboundHttp2ToHttpAdapter to allow a default data/header mode
-Extend this interface to provide an optional priority translation layer

Result:
-Priority information being correctly reported in HTTP/2 to HTTP translation layer
-Cleaner code with seperation of concerns (optional priority conversion).
Ah, sorry missed that

> Am 26.08.2014 um 16:04 schrieb Scottmitch <notifications@github.com>:
> 
> In codec-http2/src/main/java/io/netty/handler/codec/http2/InboundHttp2ToHttpAdapter.java:
> 
> > +
> > +        @Override
> > +        public void onWeightChanged(Http2Stream stream, short oldWeight) {
> > +        }
> > +
> > +        @Override
> > +        public void goingAway() {
> > +        }
> > +    }
> > +
> > +    /**
> > +     * This adaptor provides just header/data events from the HTTP message flow defined
> > +     * here <a href="http://tools.ietf.org/html/draft-ietf-httpbis-http2-14#section-8.1.">HTTP/2 Spec Message Flow</a>
> > +     */
> > +    private class MinimalHttp2ToHttpAdaptor extends Http2ConnectionListenerFrameObserver {
> > +        protected final IntObjectMap<FullHttpMessage> messageMap = new IntObjectHashMap<FullHttpMessage>();
> It is used in PriorityHttp2ToHttpAdaptor which inherits from this class.
> 
> —
> Reply to this email directly or view it on GitHub.