Date: Fri, 12 May 1995 09:10:44 -0400 (EDT) From: "Alok K. Dhir" <adhir@iagi.net> To: freebsd-hackers@FreeBSD.org Cc: Terry Lambert <terry@cs.weber.edu>, freebsd-hackers@FreeBSD.org, taob@gate.sinica.edu.tw Subject: Re: Apache + FreeBSD 2.0 benchmark results Message-ID: <Pine.BSI.3.91.950512090851.14561D-100000@bigdipper.iagi.net> In-Reply-To: <199505112230.BAA29734@lk-hp-20.hut.fi>
next in thread | previous in thread | raw e-mail | index | archive | help
How about you all take freebsd-hackers out of the cc line...? I've had it with the repeated forking quasi multitasking asychronous task processing $#@$@#!$@# ;-) On Fri, 12 May 1995, Juha Inkari wrote: > > > from. What you have is an I/O Dispatching server according to what I've > > been taught . > > I guess the point is differentiating servers in how they perform > multi-tasking. The server could dispatch several requests to different > tasks or it could process the requests syncronously consuming several > tasks for one request. Here goes yet another set of names: > > - Repeated forking heavyweight processing server. > - Multiple forked heavyweight processing server. > - Lightweight processing server. > > Also, multi-threaded or asyncronous could be added for clarification > in some contexts. The "lightweight processing server" says nothing > about the time of creation of the processing tasks, or about the > "lightness" of the thread of control, except that it should not be as > resource consuming that the "heavyweight" model. > Alok K. Dhir Internet Access Group, Inc. adhir@iagi.net (301) 652-0484 Fax: (301) 652-0649 http://www.iagi.net
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSI.3.91.950512090851.14561D-100000>