home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!spool.mu.edu!uwm.edu!csd4.csd.uwm.edu!markh
- From: markh@csd4.csd.uwm.edu (Mark)
- Newsgroups: comp.programming
- Subject: Re: Network Chat Messaging Algorithm
- Date: 23 Dec 1992 11:58:41 GMT
- Organization: Computing Services Division, University of Wisconsin - Milwaukee
- Lines: 12
- Message-ID: <1h9k9hINN670@uwm.edu>
- References: <1h8752INNn3i@darkstar.UCSC.EDU>
- NNTP-Posting-Host: 129.89.7.4
-
- In article <1h8752INNn3i@darkstar.UCSC.EDU> banshee@cats.ucsc.edu (Wailer at the Gates of Dawn) writes:
- >Fnet is a client/server system based on TCP/IP sockets. The outline of
- >communication between the client and server is as follows:
- ...
- > Specifically, the client connections are multiplexed by the server, using
- >the select() call....
- ...
- > Net lag causes unacceptable waits to all clients.
-
- Net lag is not causing those problems, select() is. Always check for blocking
- even if set in non-blocking mode, because select() sometimes blocks regardless.
- Or, better, don't use select(). Use fork().
-