MacOS as Thin Client (was: Why MacOS for Apple NCs?)

[L. Todd Heberlein]

I have found the discussion on Network Computers (NCs) interesting, and I
went digging around and found an old mail message I sent to Apple last March
(see below). I had proposed using OpenStep on the thin client, but I guess
you could substitue MacOS there.

In my diggings I also found many of the vendors producing NC computers to the
NC specification [1] are also supporting thin client technology approach
where the applications are actually running on a central server and being
displayed on the NC terminal. The commercial reasons for this are obvious:
their NC can run/display the millions of Windows and X-windows (and MacOS
soon?) applications out there as opposed to the negligible amount of 100%
Pure Java applications which are out there. For more information, see
[2][3][4].

Cheers,

Todd

[1] http://www.rdg.opengroup.org/public/pubs/catalog/x975.htm
[2] http://www.ncd.com/pnc/pnc.html
[3] http://www.tek.com/VND/PDFs/nwd-nc200.pdf
[4] http://www.wyse.com/products/winterm/4000.htm

---------- Thin Clients (or how I wasted a lunch hour) ----------
To: Leade...@apple.com
Subject: Thin clients
Date: Friday, February 28, 1997 11:31 PM

Here is yet another wonderful opportunity Apple has "stumbled into" with
their purchase of NeXT: Thin Clients

The concept of a "thin client" is hardly new, X windows technology has been
delivering such systems for years. In X windows, a computer runs a program
called a window server to which X windows programs (clients) connect.
Because of the client-server model of the X windows architecture, the
client programs and the windows server can easily run on different
machines. A wonderful example of this is the X-terminal - a very simple
computer which mainly runs a single program, the X windows server. The
actual applications run on a server, and they send their display
information (via the X windows protocol) across the network to the
X-terminal's window server.

The advantages are obvious: the X-terminals are low cost systems with
essentially zero maintenance costs. The applications, the processes
running those applications, and the data files are all contained on
servers. In essence, you have virtually all the advantages of the much
heralded "network computer."

NeXT's windowing technology also supports this capability. For fun, I used
to run programs (usually games like XoX) on other NeXT computers and
display them on mine. Keep in mind, these were 33 MHz 68040 computers.

Apple can and should take advantage of this capability. First, Apple could
lay claim to a low-cost, zero-maintenance solution made by the proponents
of network computers and the Microsoft NetPC efforts. Second, Apple can
use this approach to push high-end, high-profit servers which will host the
applications, processes, and files. Third, Apple can quickly support older
and less capable Macintoshes (see below). Fourth, Apple can support older
and less capable PCs.

SUPPORTING OLDER MACS:
The "thin client" concept is this: Apple decouples the OpenStep display
technology from the rest of OpenStep and develops this code into a
stand-alone OpenStep display server. Because it doesn't support the full
OpenStep and Mach kernel capabilities, the OpenStep display code would have
a much smaller footprint on disk and in memory, and would therefore be able
to run on smaller, older Macintoshes. The actual OpenStep programs would
run on an Apple server, so the older Macintosh with the OpenStep display
server wouldn't even need room for the program. The result: sites with
networks of older Macintosh computers could continue to use them and
preserve their investment.

Apple could also port the software to Windows (or OS/2), so people with
networks of older and less capable PCs could preserve their investments
just as the Macintosh owners could. Furthermore, it would give Apple an
opportunity to sell Apple servers into organizations which have
traditionally been a PC shops!!!

DEMAND IS THERE
The demand for this approach is there as has been seen with all the
attention given to network computers, NetPCs, and recently the Citrix
Systems story. Citrix Systems developed the same capability for Windows NT
servers and Windows clients, and Insignia Solutions ported the client code
(calling it NTRIGUE) to a variety of client systems include Macintoshes and
X-terminals. Microsoft has found enough demand from their customers for
this capability that they want to make it a standard part of their Windows
NT distribution (much to the unhappiness of Citrix Systems).

Thin clients: the demand is there, Apple has the key technology already to
do it, Microsoft is going to do it, you can help preserve existing
Macintosh sites' investments, you can sell high-profit servers, and you can
get your foot in the door of PC networks. I think Apple would be foolish
not to deliver this capability.

Todd Heberlein
Net Squared Inc.