On Fri, 21 May 2004, Bernd Eidenschink wrote: > > Ok, fine with me! But, if you want to tell this to your potential users, > > you must also give them a reason to switch. If the reason to switch > > is not to use TCL and use the AOLserver API, what is it? Users won't > > switch because they can leverage the vast knowledge they already have, > > for the simple reason they can already do that on Apache. > > Oh, there are a lot of people out there that will give AOLserver a try > if only they are able to use it with something they need anyway, let's > assume PHP for the sake of that thread.
So, if I may summarize your text, according to you AOLserver should look for wide looking users that like to experiment a bit. They will see the merits of AOLserver and start to like it. The current advertisement to new users is okay. This certainly true. I think it is for most of us the way we became AOLserver users and deeply conservative people will be the last ones who'll try it. My original point was about skepticism that a lot of people seem to have with regard to AOLserver. To do something about that, the project can advertise itself in a more friendly way to people on the website. My point was, that if you choose AOLserver, you choose Tcl and the project should be clear to people that AOLserver is not a better PHP-server than Apache, but a beautifully designed architecture on its own merits. Now you can say "we only want people with a broad view" and they will find us, so the current communication is okay. I would have a bit broader ambition and try to get more people interrested in AOLserver, actually the project is pretty small currently. And then we get again the question, why should they use AOLserver over Apache if the advantage is not the TCL oriented design? You know, I don't mind at all what the answer is, but this matter is about the focus of the project, what it would like to be etc. If you want to advertise PHP support, you should then, preferably, be better at some PHP-realted things than Apache. You can also say, "we support PHP as good as we can", but if you have choosen AOLserver you have choosen TCL. In the second case, being better than Apache is not required, being just is then a good point to target. > > So, what advantage does it then have to run PHP (or language x) on > > AOLserver instead of Apache? This a critical in the communication to potential > > users, since, likely they already use Apache. > > One advantage is that an AOLserver administrator, confronted with the > requirement to offer PHP (for WHATEVER reason), would simply add PHP to > AOLserver with no need to install Apache. Because it's AOLserver he/she > is competent in, not Apache. This scenario is the opposite of yours, > where the person already likes and runs AOLserver and does not have to > be convinced. This is a bit off topic. Of course this is true; preferably I would like to run a single webserver and simply copy php files I download into it. Remember that we're not discussing wether different languages need to be supported, the answer is "of course!!". Instead, we're discussing what the position and meaning of these alternative languages is within AOLserver. Greetings, Daniël Mantione -- 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.
