🚀 go-pugleaf

In article <1992Oct6.121213.20420@porthos.cc.bellcore.com>
jona@iscp.bellcore.com (Jon Alperin) writes: 
> Yeah,, but try to explain that the X Client runs on the network server,
>talking to the X server running on a workstation client. 8-}

You're network FILE server has the files on it.  Your X server has the
graphics on it.  You run clients where the resource you are using
isn't.

>Client/Server is at best ill-defined, since it assumes a host/terminal
>paradigm, where the client is simply performing some (few) tasks that 
>used to be handled by a host.

I strongly disagree.  Client/Server model is based on sharing
distributed resources.  When you don't have that resource, you ask
another machine for that resource.  The paradigm is much more general
than host/terminal.  The clients are typically much smarter than mere
terminals.

>If I place a printer directly on my
>ethernet net segment, and I still use terminals connected to a central
>host but allow the host to send packets directly to a printer, is this 
>C/S computing?

Yes.  The printer that you added to your network is a print server.
The host is offloading its printing needs to the printer.  The fact
that you have terminals connected to the host is non-issue.  I have a
workstation that I print from.  I have little idea of how the printers
are connected to the network.  I just type "lpr" at the prompt or
choose print from the GUI for the program I'm using and it magically
appears at the right place.

Warner
-- 
Warner Losh		imp@parcplace.COM	ParcPlace Boulder
I've almost finished my brute force solution to subtlety.