On Fri, May 21, 2004 at 11:10:31AM +0200, Dani?l Mantione wrote: > On Fri, 21 May 2004, Bernd Eidenschink wrote: > > > PHP works with AOLserver, at least some folks use it. I don't know how > > well maintained the bridge ist, nor if PHP can be compiled with 4.0, but > > supporting PHP would be absolutely no harm. I would think of it as the > > honeypot. It would allow people to use and maintain their (needed) PHP > > applications and let them eventually get used to TCL.
EXACTLY. > Yes, but it does not make sense. Why would you run AOLserver if you want > to run PHP-scripts? Even I run them on Apache. Supporting PHP might sound There are some good reasons. E.g., some OpenACS users are running PHP in AOLserver solely in order to run some webmail app which happens to be written in PHP. I don't remember whether they did so or not, but by running it inside AOLserver, they should be able to integrate its login and authentication with that of their OpenACS website. http://openacs.org/doc/current/install-squirrelmail.html http://openacs.org/forums/message-view?message_id=155447 http://openacs.org/forums/message-view?message_id=158125 http://openacs.org/forums/message-view?message_id=85405 > comfortable to people, and it'll definately help them to run their > "legacy" scripts, but it is not what AOLserver is about. AOLserver can > only be used to it full potential if TCL is used. That's just not true. I'm sure the SMLserver guys thought they were "using AOLserver to its full potential", and it lookes like they never touched any Tcl code at all, just Standard ML and C. "Using Tcl is generally the simplest and easiest way to use AOLserver to its full potential." - that's probably true. > The message to new users should be "Yes. You have to switch to TCL, but, > don't worry, we're sure you'll regret that you didn't do it before" > instead of "Switch to AOLserver, it's easy and nothing has to change for > you". No, VERY bad idea. No users HAVE to do anything, it is up to them. We're here merely to give learned and practical advice, point out alternate and better ways to solve problems, etc. "AOLserver is very powerful and very flexible, this gives you the freedom to do what you want." Personally I think Tcl is, overall, a fabulous language, and it's tight integration with AOLserver make both even better. But others, perhaps out of ignorance, don't share that view. If a whole bunch of PHP users suddenly appear, start using AOLserver, and never touch Tcl at all, that would be just fine! Once they're committed to using AOLserver at all, some of them will no doubt gradually join us in the more traditional world of AOLserver Tcl, ADP, and C code. But if they don't, cool, that's still fine. And leaving all those theoretical new PHP users aside, strong Java, PHP, and whatever support is a good thing for *ME*. Not because I have any particular plans to use Java or PHP - I don't. But AOLserver is one of my favorite tools, and all else being equal, the more problems I can potentially apply it to, the better. E.g., I'm told that TagSoup happens to be the best available parser library for messy real-world HTML, and it happens to be written in Java. If I needed to, I could probably run that in AOLserver, and that gives me warm fuzzy feelings. http://sourceforge.net/projects/tagsoup/ Similarly, I LIKE the fact that Standard ML and Python, to at least some degree, are both integrated with AOLserver. I've idly thought about looking into the doing the same for Erlang. -- Andrew Piskorski <[EMAIL PROTECTED]> http://www.piskorski.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.
