4 ms·

So basically, start the worker as soon as you see a domain in SNI. It's really interesting to see layer models and their abstractions - criticial to the develop

So basically, start the worker as soon as you see a domain in SNI. It's really interesting to see layer models and their abstractions - criticial to the development of the internet - being removed/merged/coupled in order to eek out performance.

iampims 6y ago
And given that Cloudflare is a big proponent of encrypted SNI, I wonder how this will play into it :)
- jgrahamc 6y ago
  Encrypted SNI hides the SNI from an eavesdropper and not from Cloudflare if you are connecting to a Cloudflare-managed zone.
pornel 6y ago
In my experience breaking layering leads to interesting optimizations. Another Cloudflare feature is using JPEG start-of-scan boundaries to guide HTTP/2 frame multiplexing: https://blog.cloudflare.com/parallel-streaming-of-progressive-images/ https://blog.cloudflare.com/parallel-streaming-of-progressiv... It's a total protocol layering violation, but makes images appear on screen much faster.
treis 6y ago
This doesn't seem to be quite that simple. If I have 10 workers (or 100 or 1000) for the same domain then it has to warm them all. Which maybe it does but that seems inefficient.
- hugoromano 6y ago
  For now only the route that uses domain.com.