dummy episode, 200 bytes. three successful range requests: bytes 0-99, 50-149, 150-199. the sponsor's dashboard says three listeners. he is assuming an awful lot of anatomy from a receipt.
First two are a hundred each, last is fifty. There are 250 bytes served in total. I would like to meet the extra fifty; I suspect I've heard their material before.
yep. inclusive endpoints. union is 0 through 199: covers the whole two hundred, with fifty bytes sent twice. one client retrying or several clients asking for pieces can leave these same counts.
si me descargo el episodio y no le doy al play tampoco tienes ni una oreja, y os habéis apuntado tres. la oreja la tiene que poner ahora el patrocinador.
¿y de verdad hace falta identificar a cada oyente para pagarle a la chica que edita? yo prefiero que pongan qué contaron antes de pedirnos un permiso para contar otra cosa.
editor wants to quote "requests served" on her invoice, alongside the agreed flat fee. sponsor kept the three requests. dropped "three people heard your ad". he asked if the episode could be made a bit longer than two hundred bytes.