Date: Fri, 20 Apr 2001 09:54:29 -0500 From: Tony Wells <awells@journalstar.com> To: Walter Miller <wmiller@mediaone.net> Cc: freebsd-questions@FreeBSD.ORG Subject: Re: Apache or AOLServer? Message-ID: <3AE04DA5.58B18F80@journalstar.com> References: <000c01c0c856$3dd16690$1502290a@wmiller2K> <20010418180859.B69031@cec.wustl.edu> <01041819472700.01696@eman.ynapmoc>
next in thread | previous in thread | raw e-mail | index | archive | help
I've monkeyed around with AOLserver for a couple months now and I like it. The user base is noticeably smaller than Apache, so it's kinda hard to find anyone who's familiar with it. What I liked about AOLS is that it has a built-in Tcl 8.3 interpreter and it has built-in persistent database connection pools. The only third-party module I need is the MySQL DB driver, which being the AOLS db interface is so clean, even I can understand. (And modify the driver slightly, which I did.) AOLS virtual hosts all listen on different ports, and from what I can tell AOLS doesn't do name-based virtual hosting, but the rumor is the next major release will have better virtual host support. I've read most of the Greenspun stuff about AOLS, but once you load the PHP module for Apache most of his points become moot. PHP has persistent database connections, PHP doesn't spawn another process etc... We run Apache/PHP and average about 30 SQL queries per second, with about 60/second peak, and the machine doesn't break a sweat. That said, it took a lot of work to get a stable Apache/PHP setup and to get the logs quiet. PHP isn't the only solution for dynamic content for Apache, and truthfully the options are staggering. Probably the only way to evaluate AOLserver is to download it and start messing around with it. Or you could ask the folks on the AOLserver mailing list for more information which you can join at http://www.aolserver.com/ Walter Miller wrote: > > On Wednesday 18 April 2001 04:08 pm, Andrew Hesford wrote: > > On Wed, Apr 18, 2001 at 03:23:43PM -0700, Walter Miller wrote: > > > Any chance FreeBSD would use AOLServer for their website now that it's > > > open sourced? It seems like AOLServer would be a better fit for > > > FreeBSD than Apache based on the supposed performance and > > > multi-threaded lead it has (and has had for quite a while) over > > > Apache. I'm actually trying to decide for myself which one to go for > > > although I'm leaning towards AOLServer but maybe you guys have some > > > good reasons why Apache is the way to go. > > > > Um... next time, buy the *expensive* acid, okay? > > > > There's a reason 60% of the World Wide Web is powered by Apache... not > > only is it open source, but it's stable, works well, supports a wide > > variety of modules, and is highly configurable. > > > > I've never seen AOLserver. It may be the greatest web server there ever > > was. But let me tell you what I know: > > > > 1) AOL's instant messenger clients and service are shitty on any > > platform. > > > > 2) AOL's internet service and its clients are shitty. > > > > 3) AOL owns Netscape, and Netscape is shitty. > > > > In all my experience with AOL and its products, I've never had a good > > experience. This leads me to be very cautious about anything they > > produce. > > > > It strikes me as odd that AOL would produce a web server; is this just > > the old-time Netscape server product renamed and repackaged? > > It's a product they got from taking over a company called Navisoft. > > > Until you can tell me who says that AOLserver outperforms Apache (AOL > > doesn't count), and who has had good experiences with it, I won't even > > begin to consider it as an Apache alternative. I fail to see > > multithreading as an immediate advantage. > > I'm looking for some good examples/experiences myselft - the whole reason for > this email. > > A little dated but probably still relevant: > > http://philip.greenspun.com/wtr/aolserver/introduction-1.html > http://philip.greenspun.com/wtr/aolserver/introduction-2.html > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3AE04DA5.58B18F80>