The blog of Webtide, the company behind the Jetty Java server, covering HTTP/2, threading, and Jetty releases.
HN links it in discussions of Loom virtual threads, with posts showing a million virtual threads and Jetty support, while commenters raise caution about heap use.
While this is definitely a good new, we need to be very careful. Why? Those new fancy threads are stored on heap and need to be garbage collected. If you buy into ads and believe that you can create for free millions of threads, then, well, it is not gonna work on production.
Because of this server based on new threads does not need to be more performant, Jetty server guys tested this and they were not that happy: https://webtide.com/do-looms-claims-stack-up-part-1/
Before getting too excited I advise to watch Tomasz Nurkiewicz lecture on the subject - https://www.youtube.com/watch?v=n_XRUljffu0, it explains what are the trade-offs here.
No silver bullet, again.
Now added to the small list of SPDY enabled sites as I find them:
https://www.webtide.com/
https://twitter.com
https://spdytest.com
https://spdy-twitlog.indutny.com
https://www.codecentric.de
(and of course google.com, gmail and youtube.com)
Of course the number will explode in a few months but fun to know the handful in the "early days".
ps. SPDY indicator for Firefox 11+ https://addons.mozilla.org/en-US/firefox/addon/spdy-indicator/
Take a look at conscrypt
https://github.com/google/conscrypt
According to reports into Jetty folks, using conscript for TLS, gives 10x improvements
https://webtide.com/conscrypting-native-ssl-for-jetty/
Note, that, from what I read, conscrypt is not compiled for any of the BSDs so if you are testing there, you will have to compile conscrypt yourself
I think you are on to something here and it is more about http/1.3 than http/1.1.
I am actively rejecting HTTP/2 purposely after the findings of my network protocol security analysis of the many HTTP/2 variants. It reminds me of the classic overlapping IP fragmentation packets (Windows vs. BSD).
https://webtide.com/rfc7230/
https://webtide.com/servlets-must-die-slowly/
No comments there, but you can read about his probable contributions to the continuations API in later posts maybe?
Sure we all try to implement HTTP the best we can, the difference is how fast and efficiently we do it.
From what I could find online, there are no plans to include websockets as part of HTTP/2 (according to this: https://webtide.com/http2-last-call/ ). HTTP/2 is meant to supersede all websocket use cases.