Once you've done this it would be nice if www.aolserver.com became an 'example' site for new users. The code, config, adp pages, etc. etc. should be accessible in CVS.
This could demonstrate good practice usage of the core AOLserver features, perhaps some of the more commonly used modules, and perhaps some ideas on how AOL goes about scaling AOLserver up to support the high levels of traffic it can handle. AOL must have a whole raft of monitoring, debugging, performance analysis tools for AOLserver. It would be nice if some of these made their way into the public domain too! ;-) Tim > -----Original Message----- > From: AOLserver Discussion > [mailto:[EMAIL PROTECTED] Behalf > Of Nathan Folkman > Sent: Tuesday, November 04, 2003 3:46 PM > To: [EMAIL PROTECTED] > Subject: Re: [AOLSERVER] Ns_SetRequestAuthorizeProc has no Tcl Command > > > We're working on moving www.aolserver.com to one of our own servers > again, which would be obviously an AOLserver. Once the move is > completed, should be trivial to setup the TIP code there. > > - Nathan > > Zoran Vasiljevic wrote on 11/4/03, 10:32 AM: > > > Whatever the name, what I'd like to know is how the www.aolserver.com > is working to be able to fit-in the TIP-tracker once I get it from Tcl > people. > Who is attending the site? Whom should I bug? > > Zoran -- 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. -- 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.
