What is it? Nothing happens on mobile Safari.
Nor mobile chrome. Guess I'll have to check it out later.
Works for me in mobile Chrome 63 and in mobile Firefox 55.
Ultrafast single TCP packet audio/visual experience
31–40 of 79 posts
Re: Ultrafast single TCP packet audio/visual experience
#32Earlier quoted context omitted.
At least in Linux, ICWND is set to 10 now: https://tools.ietf.org/html/rfc6928
Hm. I what the distribution of latency vs bandwidth is like, whether 14kB or 2 round trips takes longer for most people?
Probably the two round trips. A semi-nearby server might be 50ms per round trip, and in that case any connection beating 1mbps can transfer 14KB in less than two round trips. A server could easily be 150-250ms away and make those round trips far worse.
Re: Ultrafast single TCP packet audio/visual experience
#33Pro-tip: If you are doing additive synthesis and want to stack sine-waves in a harmonic series, please scale each successive n harmonic to an amplitude of 1/n. It creates a much more tolerable experience.
Further reading: https://en.wikipedia.org/wiki/Fletcher–Munson_curves
Re: Ultrafast single TCP packet audio/visual experience
#34For those you are wondering, this is a webserver that serves an HTML page in a single TCP packet. I guess ≤ 1500 bytes to avoid fragmentation - shows as 1.1KB in Chrome's network view. The HTML contains embedded JavaScript that runs a simple demo with animated ASCII and playing a LOUD changing audio tone. You can visit the demonstration website here: http://packet.city/ You can see a screenshot of the demo here: http…
So they're using p01's effect and they want to put ADs around it?
Here's hoping it's a joke. ;- )
Re: Ultrafast single TCP packet audio/visual experience
#35For those you are wondering, this is a webserver that serves an HTML page in a single TCP packet. I guess ≤ 1500 bytes to avoid fragmentation - shows as 1.1KB in Chrome's network view. The HTML contains embedded JavaScript that runs a simple demo with animated ASCII and playing a LOUD changing audio tone. You can visit the demonstration website here: http://packet.city/ You can see a screenshot of the demo here: http…
This would be really great without the audio. Due to the sound of the audio my initial reaction is to be fascinated, followed immediately by discomfort.
Over the last 5 years I've learnt to set the default sound level on my computer to "mute"
Re: Ultrafast single TCP packet audio/visual experience
#36Looks like the browser spends most of the loading time resolving DNS.
Re: Ultrafast single TCP packet audio/visual experience
#37For those you are wondering, this is a webserver that serves an HTML page in a single TCP packet. I guess ≤ 1500 bytes to avoid fragmentation - shows as 1.1KB in Chrome's network view. The HTML contains embedded JavaScript that runs a simple demo with animated ASCII and playing a LOUD changing audio tone. You can visit the demonstration website here: http://packet.city/ You can see a screenshot of the demo here: http…
Caution: loud
Opened this on my phone with headphones. I had an heartattack.
Re: Ultrafast single TCP packet audio/visual experience
#38CAUTION: This is just about popped my speakers and my eardrums, this is pretty obnoxious behaviour regardless of the technical cleverness going on.
Re: Ultrafast single TCP packet audio/visual experience
#39http://packet.city/ summary: A demo scene page that is smaller than a single IP frame and uses some flags to avoid other round trips. view-source: http://packet.city/ The page itself and view-source only work on some browsers. Use wireshark etc to see what it actually does.
Wiresharked the thing. Here's the packet sequence it reported:
-> DNS query A
-> DNS query AAAA
TCP SYN
TCP ACK
-> HTTP GET
TCP ACK
TCP FIN,ACK
Re: Ultrafast single TCP packet audio/visual experience
#40For those you are wondering, this is a webserver that serves an HTML page in a single TCP packet. I guess ≤ 1500 bytes to avoid fragmentation - shows as 1.1KB in Chrome's network view. The HTML contains embedded JavaScript that runs a simple demo with animated ASCII and playing a LOUD changing audio tone. You can visit the demonstration website here: http://packet.city/ You can see a screenshot of the demo here: http…
The limit is 1460 - the IP and TCP headers occupy 40 bytes.
Out of those another 63 are consumed by the HTTP headers.
The full TCP payload is only 1226 bytes though, and the full HTTP payload 1163 bytes. The decoded HTML document is 1546 bytes.