Boeing 747 & 777 autoland in crosswind certification video - impressive!

As a matter of curiosity, how many files is that?
26 plus 26 squared plus 26 cubed?

Digits can be in the extension also, so it's
1 + 36+ 36^2 + 36^3
The 1 is for the null extension.

Jose
--
Money: what you need when you run out of brains.
for Email, make the obvious change in the address.

Those actions were not designed to make its competitors appear inferior.
They were done in an attempt to control the standard.

Whether that's better or worse behavior is irrelevant. The fact is, the two
motivations are completely different.

By controlling the standard they ensure that other standards get
orphaned, and they get a competitive and temporal advantage unrelated to
quality. This does have the effect of "making their competitors appear
inferior", though that's not the intent I percieve.

Jose
--
Money: what you need when you run out of brains.
for Email, make the obvious change in the address.

Jay Honeck wrote:

OK, this time for sure!

I checked several. Files like the Tbird crash and supersonic flyby now display
just fine. Under the bridge still comes down with the extra mp4 extension and
will not display.

George Patterson
Drink is the curse of the land. It makes you quarrel with your neighbor.
It makes you shoot at your landlord. And it makes you miss him.

In article _GKbf.3793$SV1.533@trndny01, George Patterson
wrote:

I checked several. Files like the Tbird crash and supersonic flyby now
display
just fine. Under the bridge still comes down with the extra mp4 extension and
will not display.

George, try clearing your cache out and then try to view the video
again. I ran into the same issue after the server was fixed, but my
browser was still pulling up the (incorrectly-tagged) cached file.

I'm seeing the Under the Bridge video fine now.

--
Garner R. Miller
ATP/CFII/MEI
Clifton Park, NY =USA=
http://www.garnermiller.com/

Garner Miller wrote:

George, try clearing your cache out and then try to view the video
again.

Yep, that did it.

George Patterson
Drink is the curse of the land. It makes you quarrel with your neighbor.
It makes you shoot at your landlord. And it makes you miss him.

Ron Garret wrote:

HTTP was first described by Berners-Lee et al. in RFC 1945 in May 1996.

HTTP was invented in 1990. One of the earliest standards publications came out
in 1992. Berners-Lee had an HTML browser editor out by 1992.

http://inventors.about.com/library/inventors/blhtml.htm

George Patterson
Drink is the curse of the land. It makes you quarrel with your neighbor.
It makes you shoot at your landlord. And it makes you miss him.

In article ,
"Peter Duniho" wrote:

"Ron Garret" wrote in message
...
Well, at least we agree that something on the server side is the root
cause of the problem here.

I didn't realize that was ever in disagreement.

It doesn't "break" a standard to play a file even when the standard
doesn't
provide sufficient information to play it.

A straw man (or perhaps it's a non-sequitur). The standard does provide
enough information. What is happening here is that the server is lying
about what kind of file it is serving.

It's not a "straw man". You simply misinterpreted my meaning. By "the
standard doesn't provide sufficient information", all I mean is that the
instance of the use of the standard doesn't.

Ah, I see we have a fundamental philosophical difference here...

All the media player does is to try to make an educated guess as to what
was
actually intended

No, the media player is doing more than that. The media player is
*ignoring* the content-type information sent by the server.

As well it should, since that information is erroneous.

I tend to ignore erroneous information as well.

So when your AI flops over you just ignore it? Me, I'd get it fixed.

Are you saying that you do not?

Absolutely. Erroneous information is almost always an indication of a
problem that needs to be fixed. Just ignoring it can cause real harm.

If I roll up to a fuel pump labelled "100LL" and Jet-A comes out I'd be
pretty upset. But you would just say, "Oh, I guess when they said 100LL
they *meant* Jet-A" and figure that makes it OK.

Here's an aviation analogy: imagine that you had a magic gadget that
could convert Jet-A to 100LL. You install one of these on your
piston-powered airplane. Now when you fill up you can take either Jet-A
or 100LL. You no longer care. One day you get to an airport where the
pump marked 100LL is in fact dispensing Jet-A. From your point of view
this is not a problem. But from everyone else's point of view it is.

So... should everyone have to install one of these magic gadgets on
their planes? Or are the people without the gadget right to insist that
the fuel pumps ought to be marked correctly?

That is an exact analogy to the current situation.

No, it's not. Or if it does, it fails to prove your point.

In this current situation, Windows Media Player is the gadget, not the fuel
dispenser. The incorrectly labeled fuel dispenser is equivalent to the
server, not the media player.

That's right.

If you want to complain about anyone, complain about the server serving up
the incorrect content type information, not the media player that correctly
figures out how to play the file in spite of that incorrect information.

I am complaining about both. I am complaining about the server as the
root cause of the problem, and about the media player causing a
significant number of people to think that there is no problem and
therefore making it that much less likely that the problem will be fixed.

The problem with the media player is not so much that it plays the
video, but that it does so without providing any indication that there
is a problem. If the player put up a warning message along the lines of
"The server says this is an MP4 file but in fact it is not. This
indicates a problem with the server's configuration. Please notify the
maintainer of this site," before playing the video I would have no
quarrel with it.

What the player is doing is masking (part of) a common-mode failure and
making it appear as if it is not a common-mode failure. IMO, being
complacent about that sort of thing is the first step on the road to
disaster.

rg

In article 12Obf.6062$41.5518@trndny04,
George Patterson wrote:

Ron Garret wrote:

HTTP was first described by Berners-Lee et al. in RFC 1945 in May 1996.

HTTP was invented in 1990. One of the earliest standards publications came
out
in 1992. Berners-Lee had an HTML browser editor out by 1992.

http://inventors.about.com/library/inventors/blhtml.htm

I stand corrected.

rg

Jose wrote in news:mcCbf.9842$Lv.2337
@newssvr24.news.prodigy.net:

This affects .shb, .url, .lnk, .pif, .scf, and .shs.

It affects quite a few others too. It's not a bug. It's deliberate on
Microsoft's part. I found this out by accident
Snipola of discovery story

Furthermore, the operating system will re-super-hide these extensions
every now and then. Keep checking the registry for NeverShowExt. It
will return. Sometimes. Probably with every bug-fix and security update
they put out.
Snipola

Well, if .lnk ever gets re-hidden I'll know it immediately by my
shortcut icon descriptions. The others I may have to specifically
check for.

Brian
--
http://www.skywise711.com - Lasers, Seismology, Astronomy, Skepticism
Seismic FAQ: http://www.skywise711.com/SeismicFAQ/SeismicFAQ.html
Quake "predictions": http://www.skywise711.com/quakes/EQDB/index.html
Sed quis custodiet ipsos Custodes?
Supernews sucks - blocking google, usenet.com & newsfeeds.com posts

George Patterson wrote:
Ron Garret wrote:

HTTP was first described by Berners-Lee et al. in RFC 1945 in May 1996.


HTTP was invented in 1990. One of the earliest standards publications
came out in 1992. Berners-Lee had an HTML browser editor out by 1992.

http://inventors.about.com/library/inventors/blhtml.htm

I'm not much of a historian, but I remember the work going on at SRI
International (nee, Stanford Reasearch Institute) in the late 1970s.
This was in the group headed by Doug Engelbart who invented WYSISYG
edit-compile-debug developments, the mouse, chordic keyboards, etc.
"Hyper text" was just beginning to span networks back then. A link
simply expanded to the associated file and there was no interpreter
looking for tags. That's what Berners-Lee added.