Well, OK--JetSend isn't as sexy as the latest version of Windows (with or without a built-in browser). And it certainly isn't as fetching as a new Intel processor hitting the market (with or without allegedly pilfering Digital Equipment patents). It is, however, a really good idea.

HP noticed that using a computer isn't quite as simple as other tasks that we routinely perform, such as using a phone, launching a space shuttle or reattaching severed limbs. And though HP understands that it can't change the nature of the computer business overnight, it also understands that it's in the catbird seat concerning printers and, therefore, static image transfer. J etSend is HP's attempt to make its little corner of the computing world a bit more friendly and a tad less nitpicky.

JetSend could, if HP is lucky, mark the end of the device driver as we know it--at least for some devices. It also might put those in the file and print server business into just the file server business. Here's the idea: Eliminate the notion that says, "If you're going to use a device on a network, you must know what that device is and what it can do."

A better way to go, according to HP, is to negotiate with the device and learn its capabilities. For example, rather than having to know that you're sending data to an HP LaserJet 4MV, with firmware rev 3.2941, your computer should be able to determine if a device is a printer, if it prints in color and the resolution it supports. Then, your computer can format data for the device, using the highest quality that the two devices can negotiate. And you don't need to worry about drivers.

HP sees many applications for this technology, i ncluding computers transferring data between scanners, printers and digital cameras. These devices also could transfer data between themselves and other static image-oriented devices. Further, HP envisions the JetSend system being extended to include video and audio, or anything else that might strike the fancy of the technically tuned-in.

Every Journey Begins With a Standard Making it easy for devices, such as digital cameras, to send data to printers and scanners to ship images to computers is great. And, when it comes right down to it, JetSend is a fairly trivial technology. It's essentially a middle-layer protocol (session and presentation layers for you ISO mavens). HP has intentionally not specified any transport protocols as part of JetSend. It can run over TCP/IP, Firewire or IrDA and will probably take advantage of any future transport protocol.

HP's work is necessary, but not sufficient to make our lives with electronic gizmo's simple and straightforward. Although it is necessary to allow for multiple transports, it's also necessary to pick just a few and limit implementations to those. Further, there must be services based on those protocols. Just because two network devices have IP numbers doesn't mean they can find each other on a network. Even on a Firewire chain, it's likely that someday there will be a couple of JetSend-enabled devices; how's a simple device like a digital camera supposed to select between the printer and the PC?

On the other end of the spectrum, there's the need to support electronic commerce directly via a JetSend device. If I want to print to some hotel printer via my laptop's IrDA port, it better be as simple as pointing my laptop at the printer and hitting the print button, or I won't use it. If the hotel has my smartcard info, shouldn't my laptop be able to use any peripheral device in the hotel? I thought that was generally the idea.

HP's first step is a good one, but there's a lot more work to be done before we'll see simple, usable device-to-dev ice communications. If you want to know more about JetSend take a look at www.jetsend.hp.com. Tell them I sent you. If they still let you in, tell them what you think it will take to make JetSend the gizmo technology of the 21st century.

Art Wittmann can be reached at awittmann@nwc.com.