https://datatracker.ietf.org/doc/html/draft-toomim-httpbis-b...
Looks really stupid when transfer-encoding chunked already exists for exactly this use case.
Looks really stupid when transfer-encoding chunked already exists for exactly this use case.
Some people have suggested using chunked boundaries as a way to encode multiple responses to a subscription. Perhaps this is what you are thinking of. However, chunk boundaries cannot be relied upon to remain intact; they can be changed by intermediaries. The chunks are only an encoding of the transfer. They are not supposed to contain any semantic information.
Chunked transfer is also disallowed in http/2.