Re: Client/server..

["William W. Dyess" <dyessww@Eng.Auburn.EDU>]

> This particular discussion has been going on in the netrek arena for
> years.  Netrek was originally developed on a 14 processor sequent.  When
> you have a dozen (slow) 16 mhz 386's, you WANT to break intensive tasks up into
> several processes.  On single processor machines, however, all the context
> switching and memory usage of having multiple processes really thrashes.  
> The only real argument for multiprocess is that it makes debugging a
> little easier, as single processes can fail without taking out the whole
> server.

Several people have tried (and so far, failed) to integrate the netrek 
server into just one process.  I'm not sure of the details, but from 
listening to those trying to do it I gather that there is some difficulty 
with the network side of things.  Something about having to rewrite lots 
of the network interface code?

I'll see if I can find one of them to comment on it. 

--Bill