What the heck does his "current commitment to Apache" mean exactly?
He's engaged to marry it? His company has internal political
objections to running AOLserver behind an Apache proxy?
Or something more technical like he has current applications written
in, say, Apache mod_perl and he needs seemless and high-performance
interoperability between those apps and OpenACS? (If that example is
it, I don't see how simply replacing AOLserver with Apache for OpenACS
use would solve any of his integration problems, actually. But I
might be missing important details.)
It would be helpful to know the actual precise needs and use cases of
folks like this CTO...
