-> > Now, if adding other scripting language support could be done without -> > adding any baggage to the core -- as external modules -- I'm all for it. -> > However, I would hate to see the core get bogged down with stuff to -> > accomdate all sorts of languages if it means negative impact towards its -> > ability to fit the niche I just described. -> -> I wouldn't think that it would bog down the core if done right. Perhaps -> a few extra hooks, but not many. Note that tclperl and tclpython both -> exist and could assist in this respect (although we already have the -> python integration).
The real issue with integration is not language crosstalk, IMO -- that is a more general problem that is being solved elsewhere (e.g. tclpython). Hooking into the AOLserver internals so that Python, or Java, or Perl can all be used to serve URLs through the C API is the only AOLserver-specific work that needs to be done, and this can be done without modifying the core at all. --titus
