On Sun 15 Nov, Richard L. Peskin wrote:
> At 11:47 AM +0100 11/15/98, Hans-Martin Mosner wrote:
> > If you use TCP/IP, for example, your
> >Smalltalk process will be suspended while waiting on the socket for a
> >response, but other Smalltalk processes are free to run regardless.
> 
> I would have thought this was the case, but when I do an "update" (from the
> update server), it looks like all Smalltalk processes are blocked untilthe
> complete update is finished.
That would be because only a small part of the overall update process
involves waiting on the socket. The code has to be compiled as well...

tim

-- 
Useful random insult:- Blew the hatch before the lock sealed.
Tim Rowledge:  rowledge at interval.com (w)  +1 (650) 842-6110 (w)
 tim at sumeru.stanford.edu (h)  <http://sumeru.stanford.edu/tim>