Generally speaking our authentication method is really quick, so it would be a performance hamper if we forked for every request. It's just these 'rare' cases that mess us around - ie. kerberos server decides to take 2 minutes to return for some unknown reason.
But squid is not multi-threaded either, though it can handle a *large* amount of concurrent requests - nor does it fork. Hugh Irvine wrote: > > Hello Chris - > > No - Radiator is single-threaded at this time. > > BTW - why don't you want to use "Fork"? > > regards > > Hugh > > On Thu, 11 Jul 2002 13:06, Chris Myers wrote: > > Hugh, > > > > I'm wondering if Radiator can handle simultaneous requests > > without forking, in the same way that squid does. (i.e. > > one process - no multithreading). I know that it has been > > mentioned before on the list that the best way to do this > > was with multithreading but perl multithreading is non- > > production. Can this be done with a select loop? > > > > My problem is that if a request starts to block for an > > unexpected amount of time I would like to be able to > > handle other incoming requests. Naturally loadbalancing > > can minimize this problem but it does not solve it. > > > > Cheers, > > Chris > > -- > Radiator: the most portable, flexible and configurable RADIUS server > anywhere. Available on *NIX, *BSD, Windows 95/98/2000, NT, MacOS X. > - > Nets: internetwork inventory and management - graphical, extensible, > flexible with hardware, software, platform and database independence. -- + Chris Myers ~ [EMAIL PROTECTED] . Information Technology Services - Software Infrastructure . Ph: +61 7 3365 4017 - Mobile: 0413-009-482 - Room: 42-412 . The Prentice Building - The University of Queensland 4072 + PGP Public key available @ http://www.uq.edu.au/~uqcmyers === Archive at http://www.open.com.au/archives/radiator/ Announcements on [EMAIL PROTECTED] To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.
