| Subject | RE: [IB-Architect] Classic vs. superserver (long, very very long) |
|---|---|
| Author | Chris Knight |
| Post date | 2002-10-17T00:57:27Z |
Howdy,
I don't necessarily get a full sense of what they do and how they
should be used by a cursory browsing of the source code.
Any help would be greatly appreciated.
Regards,
Chris Knight
Systems Administrator
AIMS Independent Computer Professionals
Tel: +61 3 6334 6664 Fax: +61 3 6331 7032 Mob: +61 419 528 795
Web: http://www.aims.com.au
> -----Original Message-----Does anyone have a full list of these switches and what they do?
> From: Jim Starkey [mailto:jas@...]
> Sent: Thursday, 17 October 2002 2:49
> To: IB-Architect@yahoogroups.com; IB-Architect@yahoogroups.com
> Subject: Re: [IB-Architect] Classic vs. superserver (long, very very
> long)
>
> [snip]
>
> Unless the code has been removed, classic servers can be
> configured by a runtime switch to function as either a
> single client (forked off by inetd or xinetd) or multi-client
> (bind to 3050 and listen for connections) servers. Adding
> code to maintain a pool of child servers to which incoming
> connections are distributed sounds like a very interesting
> and general idea.
>
I don't necessarily get a full sense of what they do and how they
should be used by a cursory browsing of the source code.
Any help would be greatly appreciated.
Regards,
Chris Knight
Systems Administrator
AIMS Independent Computer Professionals
Tel: +61 3 6334 6664 Fax: +61 3 6331 7032 Mob: +61 419 528 795
Web: http://www.aims.com.au