I'll put my two cents in here.. I think the BEST approach is to have BOTH a built-in language (and which one I'll leave to you folks to argue over ;), _AND_ to support a IAC/RPC mechanism that folks can use to drive it from the language/platform of their choice. I suggest that we look at supporting XML-RPC (see <http://www.scripting.com/frontier5/xml/code/rpc.html>). It's easy to implement, platform agnostic, and is being backed by some important folks in the W3C. Leonard ---------------------------------------------------------------------------- Leonard Rosenthol <mailto:[EMAIL PROTECTED]> Designated Free Electron (612) 766-4718 (Minn) Adobe Systems Incorporated (215) 233-5270 (Philly) PGP Fingerprint: 8CC9 8878 921E C627 0BC1 15BB FC19 64A9 0016 1397
- Our first potential flame war: which scripting languag... Eric W. Sink
- Re: Our first potential flame war: which scripting... William Aoki
- Re: Our first potential flame war: which scrip... Eric W. Sink
- Re: Our first potential flame war: which s... Sean Grimes
- RE: Our first potential flame war: which scriptin... amphigory
- Re: Our first potential flame war: which scri... Leonard Rosenthol
- Re: Our first potential flame war: which scriptin... M. Dockrey
- Re: Our first potential flame war: which scriptin... Leonard Rosenthol
- RE: Our first potential flame war: which scriptin... Gavin Thomas Nicol
- RE: Our first potential flame war: which scriptin... Clive Bittlestone
- Our first potential flame war: which scripting la... Phil Beauchamp
- Re: Our first potential flame war: which scri... Eric W. Sink
- Re: Our first potential flame war: which scri... Andrew M. Kuchling
- Re: Our first potential flame war: which scriptin... Norman Lorrain
