I've been stewing over a potential new HTTP/2 non-critical INFO extension frame that can be used by client or server to pass simple diagnostic data over a connection. It would essentially be a frame for log data.
-
Show this thread
-
Frame payload would be: +-------------------------------+-------------------------------+ | Level (8) | Payload ... +-------------------------------+-------------------------------+ Where Level is an 8-bit numeric log level ...
1 reply 0 retweets 1 likeShow this thread -
That is.... fatal: 0x1 error: 0x2 warn: 0x3 info: 0x4 debug: 0x5 trace: 0x6
1 reply 0 retweets 1 likeShow this thread -
The payload would be some arbitrary sequence of bytes (typically some serialized text). The frame would be non-critical so it can be ignored.
1 reply 0 retweets 1 likeShow this thread -
A new SETTINGS Parameter to specify the MAXIMUM_INFO_LEVEL would allow a peer to communicate whether or not it wants INFO frames. A value of 0 (the default) means it does not want them
1 reply 0 retweets 1 likeShow this thread -
The INFO frame could be sent on Stream 0 or any specific Stream ID and could be sent on any locally open stream.
1 reply 0 retweets 1 likeShow this thread -
For use case, imagine things like the Beacon API and diagnostics tracing over a live connection.
3 replies 0 retweets 3 likesShow this thread -
Replying to @jasnell
Hahaha, I was just gonna ask - how is this different from Beacon? By "ignored" you mean it can be deprioritized, but not dropped right?
1 reply 0 retweets 0 likes
Well yeah guess beacon is API level, and this is protocol level. But yeah haha :D This sounds not half bad, if I understand it right :D
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.