Hey, On Fri, 16 Oct 2020, 20:09 Mirja Kuehlewind, <[email protected]> wrote:
> Not sure I understand this correctly. Without the DATA framing you would > not need any frame parsing anymore, you only have to remember that a > certain stream is converted into a forwarding stream and blinding forward > all payload from that stream. The whole point is that then no additional > HTTP logic would be need anymore. > So with quiche, a receiving endpoint calls quiche's HTTP/3 oriented poll() method. This reads from a transport stream and does HTTP/3 syntax handling e.g. checking that streams and frames are being used according too all the rules in the H3 spec. Beyond that quiche doesn't handle anything about the semantics such as request processing; thats the application's job. With a modified CONNECT definition, it doesn't change things for other types of request. I still need to do frame parsing on streams unless an application tells me otherwise. On the send side, I'd need the mirror that allows an application to request sending unframed data. That causes a bled across my separation of concerns boundary. I need to account for applications that might misuse this capability to send unframed data either accidently, or purposefully because they wish to do side step the quiche's frame checking. These complications make me nervous. Others might have a different risk assessment. Cheers Lucas >
