Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!wuarchive!gem.mps.ohio-state.edu!samsung!aplcen!boingo.med.jhu.edu!welch.jhu.edu!mjr
From: mjr@welch.jhu.edu (mjr)
Newsgroups: comp.databases
Subject: Stupid question Re: client/server model
Message-ID: <1989Nov10.015843.358@welch.jhu.edu>
Date: 10 Nov 89 01:58:43 GMT
Organization: Welch Medical Library, Baltimore Md.
Lines: 22
I.Q.: Sub-Cucumber
Shoe-Size: 9 1/2


	One thing I have often heard in the client server argument is that
it is good because it lets you get around the interferin' operating system,
and it is bad because you wind up having to re-invent the operating system.

	So, my question is: Why hasn't anyone made the server the operating
system ? Make the data server + TCP/IP + device drivers + glue the OS, boot
directly into that, and let the thing just sit and listen to a port for
requests.

	Minuses: device drivers would need to be written.
		 dedicated machine needed.

	Plusses: no operating system portability issues to worry about.
		 performance ?

	Obviously, I am oversimplifying terribly, but you get the idea.
-- 
	He was in his room half awake, half asleep. The walls of the room
seemed to alter angles, elongating and shrinking alternately, then twisting
around completely so that he was in the opposite side of the room.
	"A trick of the light and too much caffeine," he thought.    -Bauhaus