FAA KEEPS GRAPHICAL TFR PROMISE

(Teacherjh) writes:

When you connect to the internet, your computer connects to another computer
that's already connected and will provide you internet services. That is your
server.

I'd call that my ISP, gateway, router, ... but not "server".

When you request a web page, the request goes to the server. If the server has
never seen this page before, the server sends the request on down the line to
other computers connected to the internet (in a rational order) until it finds
the source, which (of course) has seen this page before.

What world are we in here? You're talking about a string of
(transparent) caching proxy servers? They communicate "in a rational
order"? So this is something like a SquidCache system?

There's very little that's truly "standard" about caching HTTP proxies.
Such broad generalizations make me cringe.

'course AOL is different. But AOL is not "the Internet".

--kyler

I'd call that my ISP, gateway, router, ... but not "server".

If it has the files on it and delivers them to you, it's a server. IT may also
be a gateway and other stuff, but in broad strokes, "server" works fine.


You're talking about a string of
(transparent) caching proxy servers?
They communicate "in a rational order"?


Yes, close enough. Of course more goes on, but it's mainly irrelevant.


There's very little that's truly "standard" about caching HTTP proxies.
Such broad generalizations make me cringe.


This is true, but in the context of explaning "ctrl-refresh" in an aviation
newsgroup, broad generalizations like this are useful. We're primarily here to
discuss flying, not internet protocols; the context of the question was how to
ensure that you get the most current FAA TFR data when you go to the site.
Caching happens in many places, and it's usually a good thing. Sometimes you
need to override it; I just gave a quickie on how and why.

Jose

--
(for Email, make the obvious changes in my address)