The key to publishing an API is having multiple vendors
actually implement it. So while I agree that an open API-based
approached to complex tasks such as Enterprise technologies
is a good idea, I just don't know how many 'vendors' will
actually take the time & money to implement it - especially
since it doesn't seem to me there's much $$ in it - Perl
is simply not seen as an 'enterprise level' programming language/platform.
It's a nice glue language that's also good for prototyping or
getting something running quickly - NOT something you base complex
Enterprise-level technologies on.
Enough of devil's advocate: I think Perl can certainly handle
'Enterprise', in fact I've implemented a perl middle-tier utilizing
sync & async messages passing including event registration & whatnot
which talked to both C & Java 'backends' over named-pipes & CLI & GUI
front-ends that worked great, but I've heard all of the snickering
& Perl-bashing vs. C (& to a lesser extent Java) about being a
'real' language...
My $.02,
Mark
------------------------------------------
Mark Ethan Trostler [EMAIL PROTECTED]
Computing Solutions http://www.zzo.com
------------------------------------------
