From owner-freebsd-hackers Wed Nov 13 02:32:48 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id CAA07048 for hackers-outgoing; Wed, 13 Nov 1996 02:32:48 -0800 (PST) Received: from whale.gu.kiev.ua ([194.93.190.4]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id CAA07039 for ; Wed, 13 Nov 1996 02:32:41 -0800 (PST) Received: from creator.gu.kiev.ua (stesin@creator.gu.kiev.ua [194.93.190.3]) by whale.gu.kiev.ua (8.7.5/8.7.3) with SMTP id MAA39434; Wed, 13 Nov 1996 12:32:34 +0200 Date: Wed, 13 Nov 1996 12:32:33 +0200 (EET) From: Andrew Stesin X-Sender: stesin@creator.gu.kiev.ua To: hackers@freebsd.org cc: squid-users@nlanr.net Subject: Programming technique for non-forking servers? In-Reply-To: <199611130952.JAA17498@corp.netcom.net.uk> Message-ID: X-NCC-RegID: ua.gu MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hello people, can anyone point me to some book, or URL(s), where the programming technique for writing non-forking network server daemons is described in details? with caveats, non-obvious places... I mean those like Squid, Harvest cached, probably Gated (there is also a non-forking WWW server somewhere, but I forgot it's name, for a pity). AFAIK they are written around a huge select(), and are using asynchronous I/O. Yes, there are sources, but I'd really like to read some general theory on the subject. Thanks in advanse! -- Best, Andrew Stesin nic-hdl: ST73-RIPE