One of the most misunderstood and largely undervalued magical acts is the adoption of a magical name, as is customary in the Western tradition of magick. In the past this has been taken very seriously by secret magical societies, as it sometimes is today, but usually for the wrong reasons. It is common to be attracted to magick simply for the fun of magical culture—dressing up in extravagant robes, speaking archaic barbarous words in a booming voice, meeting up in dark, secret places with fellow conspirators against the norm, and announcing yourself as Prometheon the Grand Arch Master of the Pyramid. Magick attracts the pretentious like flies to shit, and Lord knows there are too many ham magicians out there who take themselves too damn seriously.
With postmodernism came Chaos Magic and Discordianism, and the advent of the humorous magical name—after all, magick doesn’t need to be serious in order for it to work, does it? Prometheon became Potatoface the Slowly Reclining, and magick became a bit of a laugh. Magick also attracts yahoos like flies to shit, and there are too many ham magicians out there who think themselves too damn funny.
I have often described my work in the 802.11 working group as the
best job I ever had, even though it was a part-time volunteer position
that came without pay. As a regular attendee, I had a ringside seat for
much of the 802.11n standardization effort, culminating in a vote in the
summer of 2009 to approve the task groups final draft. Procedurally, it
was a vote like many others I attended, but there was an electricity in
the room. After years of exertions to meet the yearning of users for more
speed, we were delivering a long-awaited standard. Even though the outcome
of that final vote was not in doubt, I went to that meeting in part so
that I could say I was there. As it turns out, I do have an interesting
story to tell because the final vote was 53 in favor and one against
proceeding, and many people want to understand why there was one no
When I started with wireless LANs, it would have been unthinkable to
use them as the primary method of connecting to a network. By delivering
802.11n, some of the smartest people I know have made it unthinkable not
to do so. For most practical purposes, wireless networks are now on par
with Ethernet. While wireless networks may seem like the obvious choice,
few have a firsthand appreciation for technical and intellectual firepower
trained within the 802.11 working group that makes it possible.
OK! You've decided to take the plunge: you're switching to the Mac. Well, although you
might think you're a Mac island in a vast sea of Windows, you're far from alone. Apple is on a
roll, and millions of people are buying Macs, many of them for the first time.
When PCs seem to be everywhere, why should you be using a Mac? Let's take a look.
PC stands for personal computer, of course.
But in this book and in the common vernacular, PC is a shorthand term
for a personal computer running Microsoft Windows, as opposed to a Macintosh computer
running Mac OS X.
People have various reasons for buying and using Macintosh computers. Here are some
Macs are stable. In general, fewer weird and
unreliable things happen when you're using a Mac. Programs don't crash or freeze as
often. Inexplicable problems, such as no sound from the computer or the mouse not
working, are almost unknown. And although applications occasionally misbehave, full
system crashes (the equivalent of the dreaded Blue Screen of Death in Windows) are
If HTTP is the Internet's courier, HTTP messages are the packages it uses
to move things around. In Chapter 1, we showed how
HTTP programs send each other messages to get work done. This chapter
tells you all about HTTP messageshow to create them and how to
understand them. After reading this chapter, you'll
know most of what you need to know to write your own HTTP
applications. In particular, you'll understand:
How messages flow
The three parts of HTTP messages (start line, headers, and entity
The differences between request and response messages
The various functions (methods) that request messages support
The various status codes that are returned with response messages
What the various HTTP headers do
messages are the blocks of data sent between HTTP applications. These
blocks of data begin with some text
describing the message contents and meaning, followed by optional
data. These messages flow between clients, servers, and proxies. The
"downstream" describe message