Re: [whatwg/fetch] CORS-safelisted request-headers and Client Hints (#1006)

@yutakahirano said:

> Can you tell me why they hate CORS preflight? Is that for the additional round-trip, or the server implementation cost?

Video streaming is moving towards solving low-latency streaming challenges. Conventionally, a stream consists of a sequence of segments and each video segment has a URL from where it can be retrieved. Low-latency designs include shorter segment durations, or intra-segment fetches (sub-URLs for want of a better description). Both approaches increase the frequency of requests by a varying degree. Some deployments feel the burden of increased requests per second, be it the cost to serve a request, or the additional overhead of request logging etc.

So in the face of already having to handle more requests/second to solve a streaming technical challenge, the requirement to also double that due to CORS becomes troublesome.


-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/issues/1006#issuecomment-600094900