Mobile Devices in the Enterprise

Vol. 9 No. 7 – July 2011

Mobile Devices in the Enterprise

Articles

Arrogance in Business Planning

Technology business plans that assume no competition (ever)

Arrogance in Business Planning

Technology business plans that assume no competition (ever)


Paul Vixie, Internet Systems Consortium


In the Internet addressing and naming market there's a lot of competition, margins are thin, and the premiums on good planning and good execution are nowhere higher. To survive, investors and entrepreneurs have to be bold. Some entrepreneurs, however, go beyond "bold" and enter the territory of "arrogant" by making the wild assumption that they will have no competitors if they create a new and profitable niche. So it is with those who would unilaterally supplant or redraw the existing Internet resource governance or allocation systems. Because alternative DNS (Domain Name System) roots provide such a well-proved and well-understood example of this kind of arrogance, this article begins with a short slog through that swamp before discussing the more current and topical matter of alternative numbering Whois.


Alternative DNS Roots

The DNS root is the dictionary of top-level domain names such as .COM or .US. It is managed cooperatively and transparently by a community that includes the IAB (Internet Activities Board), which designates and recognizes the IANA (Internet Assigned Number Authority); the U.S. DoC (Department of Commerce), which contracts for IANA services; and ICANN (Internet Corporation for Assigned Names and Numbers), which operates the IANA functions under that contract. The IANA functions contract includes among other things the job of editing the DNS root zone to add new top-level domain names such as .XXX. Each of these entities (IAB, U.S. DoC, ICANN) is itself a multistakeholder body that engages with the community to gather input to the decisions it makes about DNS. This governance model is imperfect, but it has worked for a long time and continues to evolve.

by Paul Vixie

File-system Litter

Cleaning up your storage space quickly and efficiently

File-system Litter

Cleaning up your storage space quickly and efficiently


Dear KV,

We recently ran out of storage space on a very large file server—one with many terabytes of space—and upon closer inspection we found that it was just one employee who had used it all up. The space was taken up almost exclusively by small files that were the result of running some data-analysis scripts. These files were completely unnecessary after they had been read once. The code that generated the files had no good way of cleaning them up once they had been created; it just went on believing that storage was infinite. Now we've had to put quotas on our file servers and, of course, deal with weekly cries for more disk space. Surely there is a better way of dealing with this problem than clamping down on everyone for fear that one of them will do the wrong thing.

by George Neville-Neil

The Most Expensive One-byte Mistake

Did Ken, Dennis, and Brian choose wrong with NUL-terminated text strings?

The Most Expensive One-byte Mistake

Did Ken, Dennis, and Brian choose wrong with NUL-terminated text strings?


Poul-Henning Kamp


IT both drives and implements the modern Western-style economy. Thus, we regularly see headlines about staggeringly large amounts of money connected with IT mistakes. Which IT or CS decision has resulted in the most expensive mistake?

Not long ago, a fair number of pundits were doing a lot of hand waving about the financial implications of Sony's troubles with its PlayStation Network, but an event like that does not count here. In my school days, I talked with an inspector from The Guinness Book of World Records who explained that for something to be "a true record," it could not be a mere accident; there had to be direct causation starting with human intent (i.e., we stuffed 26 high school students into our music teacher's Volkswagen Beetle and closed the doors).

by Poul-Henning Kamp

Articles

The Pain of Implementing LINQ Providers

It's no easy task for NoSQL

The Pain of Implementing LINQ Providers

It's no easy task for NoSQL

Oren Eini, aka Ayende Rahien


I remember sitting on the edge of my seat watching the 2005 PDC (Professional Developers Conference) videos that first showed LINQ (Language Integrated Query). I wanted LINQ: it offered just about everything that I could hope for to make working with data easy.

The impetus for building queries into the language is quite simple; it is something that is used all the time; and the promise of a unified querying model is good enough, even before you add all the language goodies that were dropped on us. Being able to write in C# and have the database magically understand what I am doing? Awesome! Getting compilation errors from Visual Studio, rather than runtime errors at testing (or worse, production)? Wonderful! Getting rid of most SQL injection issues? Amazing!

by Oren Eini