Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!intercon!news From: amanda@mermaid.intercon.com (Amanda Walker) Newsgroups: comp.protocols.nfs Subject: Re: NeFS -- where is the multiplexer? Message-ID: <269B66DF.3F5D@intercon.com> Date: 11 Jul 90 17:50:23 GMT References: <1086@cluster.cs.su.oz> <138584@sun.Eng.Sun.COM> <2494@sequent.cs.qmw.ac.uk> Sender: usenet@intercon.com (USENET The Magnificent) Reply-To: amanda@mermaid.intercon.com (Amanda Walker) Organization: InterCon Systems Corporation, Herndon, VA Lines: 15 In article <2494@sequent.cs.qmw.ac.uk>, liam@cs.qmw.ac.uk (William Roberts) writes: > Irrelevant - if I ask the server to calculate pi to a million > decimal paces and then read a block, I should expect it to take > a long time. The people who are in trouble are the other > clients expecting to see the NeFS server handle the simple > request they sent it less than a second ago. Just because the 'language' is single-threaded doesn't mean that the server implementation is. The fact that one client connection will block on a long operation has nothing to do with other connections... -- Amanda Walker InterCon Systems Corporation