Taking another look at the problems surrounding the term "payload", I went to see what was being used in h2 (RFC7540) and HTTP/3. Unfortunately, they use both "payload body" (h2, 7230) / "payload data" (h3, http-core) and also "frame payload" (h2, h3).
So, at various times, DATA payload != payload data, but a DATA payload might contain the payload data if it happens to be the only DATA frame.
Just shoot me.
The text was updated successfully, but these errors were encountered:
Yes, I'd like to decide this editorial change ASAP, but we can also prepare an editorial PR for HTTP/3 in parallel for @MikeBishop. That would be a much smaller change since most usage of payload in that document refer to frame payloads.
Taking another look at the problems surrounding the term "payload", I went to see what was being used in h2 (RFC7540) and HTTP/3. Unfortunately, they use both "payload body" (h2, 7230) / "payload data" (h3, http-core) and also "frame payload" (h2, h3).
So, at various times, DATA payload != payload data, but a DATA payload might contain the payload data if it happens to be the only DATA frame.
Just shoot me.
The text was updated successfully, but these errors were encountered: