31–40 of 149 posts
Without something to push UDP usage its possible we could end up with a TCP-only Internet that would make P2P connectivity more or less impossible.
Could that explain this : the new UI, appart from being terrible, is often seeing slowdowns for me ?
Is this possible with NodeJS + express already? I didn't see any package for that or config
Earlier quoted context omitted.
Where can I put my money on cache coherency?
I’ll take that bet and I will give you a generous 1:10 bet odds ratio. So, if you give me $1000 dollars as your stake then: - If you are wrong I get to keep the whole $1000 - If you are correct then I will give you $100 of your money back. (Leaving me with $900 of your money still hehe). In other words what I am saying is, I think you are correct in what you said ;)
Like craps odds when betting on the don't side, where you win less than what you bet.
But it's important to point out that even with 1 for 10 odds, you still get your original stake back plus the extra 1.
Is this possible with NodeJS + express already? I didn't see any package for that or config
TLDR: we are a few years out from this being anything but experimental in node.
Is this possible with NodeJS + express already? I didn't see any package for that or config
For people running apps behind Cloudfront/Fastly/Cloudflare, is it similar to h2 where it can be enabled at the CDN level, or load balancer?
Essentially, the core of standard HTTP requests and responses (method, path, headers, response code) is fairly unchanged since HTTP/1.0, and what's changed is how those requests/responses are encoded and carried.
For Chrome users, this open source extension will tell you what protocol the browser is using for each website being accessed: https://chrome.google.com/webstore/detail/http-indicator/hgc...
Unfortunately permissions to access everything on every website are way to broad for a niche extension like this. There's no guarantee it won't be sold to a malware developer in a month. If you want to use it, I suggest cloning the repo and loading it as an unpacked extension to avoid auto updates.
I am really happy Google and others are pushing QUIC, but for only one main reason: networks that disallow UDP will now be considered "broken." Without something to push UDP usage its possible we could end up with a TCP-only Internet that would make P2P connectivity more or less impossible.
For Chrome users, this open source extension will tell you what protocol the browser is using for each website being accessed: https://chrome.google.com/webstore/detail/http-indicator/hgc...
Unfortunately permissions to access everything on every website are way to broad for a niche extension like this. There's no guarantee it won't be sold to a malware developer in a month. If you want to use it, I suggest cloning the repo and loading it as an unpacked extension to avoid auto updates.
performance.getEntriesByType("navigation")[0].nextHopProtocol
This one is not hard to audit but in current model should be done by each user.