HTTP/2 Data Decompression

Motivation:
The HTTP/2 codec does not provide a way to decompress data. This functionality is supported by the HTTP codec and is expected to be a commonly used feature.

Modifications:
-The Http2FrameReader will be modified to allow hooks for decompression
-New classes which detect the decompression from HTTP/2 header frames and uses that decompression when HTTP/2 data frames come in
-New unit tests

Result:
The HTTP/2 codec will provide a means to support data decompression
I like the idea, and I don't think the typical channel read timer netty supports will work because we are talking about timing out individual streams.  Could we do it in such a way as to keep the overhead low?  I can think of at least 2 approaches:
1. setting/resetting/canceling a timer for every stream (lots of timer events and callbacks/listeners)
2. 1 general timer per connection (do we have to worry about synchronization when looking at the list of "active" streams?)
 - each stream records a time stamp of last activity (i.e. nanoTime) OR
 - each stream records a boolean "wasused" flag which is reset when the general timer fires

Is this inline with what you were thinking?