Subject Re: [Firebird-Architect] Re: GUID Key Fields
Author Jim Starkey
David Johnson wrote:

>>>AFAICR, DEC invented UUIDs. Microsoft came up with
>>>the name GUID I believe...
Nope. You made that up from scratch.

UUIDs came from Apollo. They were picked up by the delusional prima
donnas at OSF, who didn't do diddle squat. Microsoft knew a good thing
when they saw it and claimed it as their own. DEC had it's last
original idea in the early 1980s. The hardcore DECcies are hanging out
in Hawaii waiting for TCP/IP to die so they can take over the world with
DECnet ISO transport binding.

>Conformance to the IETF specification is the criterion for a guarantee
>of uniqueness. Paul Leach of Microsoft is the current "owner" of the
>specification document.
Paul Leach of MICROSOFT!!!!!???? Tell me it ain't so!!!! Surely you
mean Paul Leach of Apollo Computer.

I've told the story a number of times about Interbase V3. It was ready
to ship, but our very devoted guys in support found a rare but
reproducable hang on Apollo. After a great deal of head banging we
isolated the problem to a thread switch problem, which was duly bounced
up to Apollo. Sometime later, I got a call from Paul Leach, presumably
the same Paul Leach, explaining that we had turned up a problem in their
OS that couldn't handle a signal during a thread context switch. That
lead to rewrite of the lock and thread managers and a six month slip in
the release. That was pretty embarassing, but I hadn't experienced

>The only mechanism that is guaranteed to be unique is the mechanism that
>uses the MAC address and the system clock as the foundation. It has the
>side effect of identifying the primary MAC of the generating machine,
>which M$oft obviously thought was a security issue, but which also
>provides fringe benefits to some distributed apps.
UUIDs are necessary for systems lacking central management. With
central management, you can do much, much better.

>Support for the data type, which is becoming more frequently used over
>time, is not the same as endorsement.
Let's not confuse a problem with a perspective work around.