Re: Re: Integrating Perl into language independent networked applications

I second that; from my own experience: for easy integration from the java-side use SOAP; I guess the C/C++ side will have a useable SOAP implementation too. Besides SOAP::Lite are a whole bunch of modules on CPAN waiting to ease your pain in implementing the middleware.

SOAP has a bit more to offer compared against XMP::RPC, is nevertheless easy to handle and as good a standard as any other xml-based standard I've seen ;).

regards,
tomte

An intellectual is someone whose mind watches itself.
-- Albert Camus

Comment on Re: Re: Integrating Perl into language independent networked applications

Replies are listed 'Best First'.
Re: Re: Re: Integrating Perl into language independent networked applications by flyingmoose (Priest) on May 18, 2004 at 13:50 UTC
Except SOAP is a bloated designed-by-commitee implementation that has a lot of features you probably don't need :) My suggestion is keep it simple! XML-RPC with a single-parameter to each function, that being an XML serialized object (or equivalent) will be much easier to process and read. And don't forget to encrypt the stream!	[reply]
Re: Re: Re: Re: Integrating Perl into language independent networked applications by rob_au (Abbot) on May 19, 2004 at 09:20 UTC
Except SOAP is a bloated designed-by-commitee implementation that has a lot of features you probably don't need. Moreover, the latency on many SOAP implementations is also a concern when compared to similar CORBA or RPC implementations - See http://www.caip.rutgers.edu/TASS L/Papers/p2p-p2pws02-soap.pdf. `perl -le "print unpack'N', pack'B32', '00000000000000000000001011011100'"`	[reply]


Keep It Simple, Stupid
	PerlMonks