HTTP/2 Stream read/write liveness checks

[Scottmitch]

HTTP/2 provides multiplexing which is a mechanism designed to allow multiple logical data transfers over the same channel. Each one of these logical data transfers is called a stream. Netty currently does not provide a way to detect inactive streams the way IdleStateHandler, ReadTimeoutHandler, and WriteTimeoutHandler provides a mechanism to detect an inactive channel. This would be a nice feature to have and may help simplify usage of this codec, and keeping resources lower on production deployments where potentially malicious or just general non-responsive clients (or servers) may exists.

[Scottmitch]

@nmittler - This is carry over from our discussion started in #2872.

[Scottmitch]

taking assignment to keep track...nothing immediately planned on this...

[nmittler]

@Scottmitch is this an old issue? I would think the topic of stream lifecycle management has been overtaken by #3448 and #3544

[Scottmitch]

@nmittler - Yes this is an old issue, but I think it is still valid. This is more about providing "aliveness" checks on individual streams. I updated the title of the issue to clarify.

[nmittler]

ah ok, do we really think this is important enough to target for 4.1.0.Beta5? Is it something you have an immediate need for?

[Scottmitch]

@nmittler - Nope. Thanks for pointing that out...just habit...went on a click spree.