There are two big buckets you can group applications and content into: static (images, js, css, static html, etc.) and dynamic (adp, php, etc.). AOLserver is optimized for the latter, dynamic applications. We have a completely separate server that we use for serving static assests and sites. The server is even single threaded.
That said, the new design of AOLserver 4.x makes it possible to provide this functionality as an add on module to AOLserver, and is something we'll be looking at. No final decisions have made in regards to this yet, so we're not sure if this would even be something we'd open source. I'll keep you posted. In the mean time, you might want to look at solutions such as Tux. Hope this helps. - Nathan Bas Scheffers wrote on 11/21/03, 1:56 PM: > It sounds to me like most of these sites will be running static HTML. > Somebody correct me if I am wrong, but isn't AOLserver not the fastest in > that role? I know in the past some, shall we say less enlightened, souls > branded it as a bad server because it wasn't very fast in their > "benchmarks", not realising they put it on the wrong bench. > > Bas. -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
