[183709] in North American Network Operators' Group
Re: BGAN Optimized Laptops
daemon@ATHENA.MIT.EDU (Eric Tykwinski)
Thu Sep 10 23:50:56 2015
X-Original-To: nanog@nanog.org
From: Eric Tykwinski <eric-list@truenet.com>
In-Reply-To: <CAEmG1=oTiv8UGYEaTjSVy0H8GO1WiWswNr7g4eTozX5gitYBmQ@mail.gmail.com>
Date: Thu, 10 Sep 2015 23:50:45 -0400
To: Matthew Petach <mpetach@netflight.com>
Cc: nanog list <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org
Matt=E2=80=99s totally correct on the browser requesting the info, so =
it=E2=80=99s up to the client to decide what to download even obfuscated =
javascript links.
My question would be how far can compression take you for something like =
Opera which does some compression in browser with a caching server? I =
figure a lot of websites are probably using more uncompressed formats =
like PNG, which can probably be compressed a bit more, but it=E2=80=99s =
still like taking a tar ball. If a server in sending gzip=E2=80=99d =
text and the browser/cache are compressing that how much more can be =
gained? Compression of compression with even more compression to me is =
probably more like a downward spiral.
> On Sep 10, 2015, at 10:54 PM, Matthew Petach <mpetach@netflight.com> =
wrote:
>=20
> On Thu, Sep 10, 2015 at 6:14 PM, Scott Weeks <surfer@mauigateway.com> =
wrote:
>>=20
> ...
>>=20
>> Someone told me that there is a way for the browser to say
>> to the web server, send me only the parts of the web page I
>> request. For example, send me everything but the flash and
>> images. Being a browser wuss I thought the web server just
>> sent everything and the browser decided whether to display
>> it or not. That would mean the data already was transferred
>> over the expensive sat link incurring the data costs.
>>=20
>> scott
>=20
> Just wanted to clear one point up...
>=20
> The web is *not* a "push" model; it's a "pull" model.
>=20
> The HTML document is nothing but a text document
> which has references to other elements that are
> available to the browser, should it choose to
> request them; but it is incumbent upon the
> browser to request each and every one of
> those other elements from the server before
> they are transferred. The server will not send
> something that was not first requested by the
> browser.
>=20
> It's misunderstandings like this that make content
> providers twitch every time an eyeball network
> says "well you're *sending* all this data at my
> network" -- absolutely nothing is being sent
> that was not explicitly requested by the browser
> first. ^_^;
>=20
> Thanks!
>=20
> Matt
