in reply to Re: Re: Perl SOAPDish?
in thread Perl SOAPDish?

interoperability of Java Application server tools and applications should(will?) be handled by an evolution of SOAP and XML Schema standards

Sorry, but SOAP is horrible if you're looking for any kind of efficiency. Serialising to ASCII on one end, parsing XML on the other, all over HTTP... eeeuuurrrggghh. It's fine for simplicity and getting something going without much work, but it's no replacement for RMI if you're all-Java already. And there's also the lack of security to worry about, too.

AND that fact that the SUN / Microsoft war limits Sun Java's transactional access to the Microsoft world via RMI or IIOP, (i.e. Denial of Sun Java access to the COM world) it is a perfect fit.

There are tons of Java-COM bridges out there, you know.

-- Yoz

Replies are listed 'Best First'.
Re: Re: Re: Re: Perl SOAPDish?
by coreolyn (Parson) on Feb 01, 2001 at 23:23 UTC

    There are tons of Java-COM bridges out there, you know.

    Open Source and Microsoft supported? I'd love a reference if you have one. I'm aware of Sun's but haven't seen any others.

    The more I look at middleware technologies the more I realize XML routing and distribution is more the game than even the objects themselves. It seems to me that Perl would be more adaptable to the changing standards surrounding distributed technologies and could provide a common interface into and out of Java (J2EE) (and whatever new technology comes down the pike), and use LDAP verification for security. I guess I need to determine efficiency of Java vrs Perl in that area, (or just be assimulated and say to hell with it :)

    coreolyn -If all you have is a hammer, everything looks like a nail - Baruch's Observation
[reply]

In Section Meditations