Michael Welzl
Michael Welzl
+1, I'd love to have this! I wonder, are you folks aware of this? https://github.com/niavlys/admob4kivy it seems old, but maybe it's useful to figure out how to make things work...
Having read all this (many thanks for your help, @LPardue !) I wanted to add my 2 cents - as I stumbled over this paragraph and wanted to make sure...
About "usually": it depends on the queue length (the longer, the more likely), and pacing will also make it more likely to be too high. I suspect it often is,...
If you look at the plots in the slides, you'll see that the chance of having a "we have saturated the network, and hence will have a double loss with...
Am I misreading this? Section 2.3 says that the limit is 2 * SMSS ("MAY use L=2*SMSS bytes and MUST NOT use L > 2*SMSS bytes"). I talked about slow...
... but this is QUIC, not TCP. From a quick (tsk) look, RFC 9002 doesn't seem to specify such a limit at all.
It's just a little too slow in slow start. Yes, the time gaps get smaller, but you also send twice as many packets / RTT. I'm attaching an Excel sheet...
Hi! Sorry, 0.8 came from me: that was me not remembering our own RFC correctly :-) about Netflix, Grenville was involved with this work just before he joined, and of...