Re: Re: Apache Scripting Architecture

On 6 Nov 98, at 13:43, Rasmus Lerdorf wrote: > > Apache <-API(A)-> Scripting Engine <-API(B)-> Script Interpreter > > A clearly > defined API(B) would definitely be a cool thing to have, but you would > first need to define exactly what belongs on the engine side and what > belongs on the interpreter side. In order for this to work, people who > are intimately familiar with Mozilla JS, PHP and Perl need to be involved > in creating this API. I don't see how a single person can sit down and > define a useful API. Sure, something can be written down and it may make > a lot of sense on paper, but I can pretty much guarantee that it won't fit > any realworld situations unless the person has done *a lot* of homework. > > On the API(B) side it is a bit > overwhelming for me right now. I can't wrap my head around the entire > problem yet. Rasmus, I might not have a correct understanding of where this is leading, but isn't API(B) what ASP uses to allow using different scripting languages? Dave ---------------------------------------------------------------------- Dave Walton Webmaster, Postmaster Nordic Entertainment Worldwide walton@nordicdms.com http://www.nordicdms.com ---------------------------------------------------------------------- -- PHP Development Mailing List http://www.php.net/ To unsubscribe send an empty message to php-dev-unsubscribe@lists.php.net For help: php-dev-help@lists.php.net