Free Newsletters
Technology & Business Daily

InfoWorld
Log-in | Register

  Tuesday, February 25, 2003 

Ari Pernick on HTTP kernelization in Windows Server 2003

Ari Pernick offers insight into the HTTP.SYS kernelization of (some of) the HTTP stack in Windows Server 2003:

Well, it's a scary change, but hopefully appropriate. The chunk of the HTTP stack that we put in the kernel was the routing part. In the same way that the kernel routes different socket ports to different applications and servers running in different accounts, Http.sys routes different url namespaces. [Doubt's Log]
He goes on to say a bit more about the whys and wherefores. Thanks for the update, Ari!

 

ENUM and the loss of practical obscurity

Michael Froomkin, writing about ENUM, the proposal to converge the phone directory and DNS, says:

As currently specified, ENUM's intersection with the DNS creates a major privacy problem for the average person. [ICANN Watch, via Privacy Digest]

Froomkin elsewhere cites Parsing Hype From Hope: Will ENUM Spark Changes In Telecom?, by Rod Dixon, who asks:

Is ICANN ready to manage the deployment of what is likely to be a ubiquitous, global, telephone system? I doubt that anyone would think so today, but, if not ICANN, who? [CircleID]
Even more than who, I wonder: how? Consider this bag of Google tricks, which were undocumented when first reported by ResearchBuzz News a year ago:

http://www.google.com/search?q=phonebook:udell,nh

http://www.google.com/search?q=phonebook:603-355-8980

I'd say the cat's most of the way out of the bag already. Public information is, well, public. Is it it even theoretically possible to stuff the cat back into the bag? I don't see how we can legislate practical obscurity back into existence.

We might, however, use public information more intelligently as we converge telephone- and computer-based communication. Today I can only use Caller ID information to screen an incoming call. In a converged scenario, the call might carry a signed URL; the URL might encode the calling number and other query parameters (e.g., homepage, weblog address) in a Google search; my PC could be displaying the results of that query as I decide whether to pick up the phone.

 

Dancing with the devil

Blue Screen of Death
Alexander SPK Windows
While trying to stabilize a Windows server yesterday, Dave Winer pointed to a symphony of BSODs and wrote:

Windows itself is stable, but the server junk they throw on top of it blue screens, probably because MS engineers don't feel that they have to follow the rules, and they have access to the OS source code. Scripting News
My impression is that it's not access to source code that causes these problems, but rather, dancing with the devil at ring 0. Anybody who writes a device driver has to do that dance. Of course, the increasing kernelization of servers, for performance, does make them more device-driver-like. In Windows Server 2003, for example, the HTTP stack moves into the kernel -- a prospect that is both exciting and scary.

I'm not an expert in these matters, but I know someone who is: Dirk Smith, at Alexander LAN. (He started at NuMega, which was a really good place to learn how to dance with the devil.) Dirk called me the other day -- we hadn't spoken in years -- to remind me that his Server Protection Kit, which I had originally known as a NetWare product, is also availble for Windows. I always thought you really needed to have the NetWare product, because Novell's philosophy was to run all add-on services (NetWare Loadable Modules) at ring 0. But somehow the notion of an abend analyzer for Windows has always seemed optional.

It's odd, isn't it? Nowadays, user-mode applications that explode will offer to send their entrails to someone who can read them. When your whole system explodes, though, the entrails spew to the screen -- and maybe to a memory dump file -- but there's no-one to read them. The IT guys play the tweak-and-reboot game while inconvenienced users wait. I haven't tested Dirk's product, but if it's your job to keep Windows servers running stably, you might want to take a look at it.

Of course, the definition of "server" has gotten pretty fuzzy nowadays. Windows XP Home Edition is a desktop OS in name only. XP Home and Windows Server 2003 share a whole lot of DNA. And increasingly, "desktop" OSs are running "server" applications -- Radio UserLand, Groove. It's reasonable for IT pros to look to third-party providers, like Alexander LAN, for professional-grade abend analysis tools. But it would also make sense, I think, to roll a basic version of that capability right into the OS. That goes for Mac OS X too, I should add. It's another example of a desktop OS in name only. It's mostly stable, but not 100%, and when things go wrong I never have any clue as to why.

 


Recent Entries


















































Sponsored Technology Links

 
 
 HOME  NEWS  BLOGS  PODCASTS  VIDEOS  TECHNOLOGIES  TEST CENTER  EVENTS  CAREERS   About | Advertise | Awards | RSS | Contact Us 

Copyright © 2008, Reprints, Permissions, Licensing, IDG Network, Privacy Policy, Terms of Service.
All Rights reserved. InfoWorld is a leading publisher of technology information and product reviews on topics including viruses,
phishing, worms, firewalls, security, servers, storage, networking, wireless, databases, and web services.

CIO :: ComputerWorld :: CSO :: Demo :: GamePro :: Games.net :: IDG Connect :: IDG World Expo
Industry Standard :: IT World :: JavaWorld :: LinuxWorld :: MacUser :: Macworld :: Network World :: PC World :: Playlist