* John Sequeira <[EMAIL PROTECTED]> [20031103 15:46]: > If your app was written portably enough to run under CGI, then I would > recommend going that route with AOLServer. > > If you want a performance boost, look into persistent perl, SpeedyCGI > or FastCGI (using the cgi2fastcgi bridge, since AOLServer doesn't > support FastCGI). There might be slight code modifications required to > keep the code from exiting (see perldoc for CGI::Fast etc), but it > shouldn't be more than a handful of lines.
Thanks, SpeedyCGI looks like exactly what I need here. The code that should run from aolserver was developed by someone else ( http://sourceforge.net/projects/oma/ ) but slight code modifications are not a problem. The actual purpose is to ease installation and maintainance overhead for an application that runs on aolserver and needs this external perl app as well. Using the way you suggested spares the trouble of having to additionally install and run apache. What would be the cgi2fastcgi bridge - does it have any advantages over SpeedyCGI? I didn't find anything regarding this on google. Thanks for the hint regarding Solaris - fortunately it's going to be deployed to Linux mainly. cheers, Til -- http://tsinger.com -- 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.
