3 ms·
I guess this works by keeping the connexion alive and streaming packets of data, taking advantage of the browsers capacity to render HTML before the whole sourc
by netgusto 9y ago
I guess this works by keeping the connexion alive and streaming packets of data, taking advantage of the browsers capacity to render HTML before the whole source is actually loaded.
OP?
- wybiral 9y agoCorrect. It's a small Golang server that keeps the connection alive with chunked transfer encoding. From the browser's perspective it's like a really slowly loading page. The connection count is updated by sending some inline CSS ::before content changes.