Kaare Rasmussen wrote:
I agree, using bloated, overweight standards often ticks me off, but in SOAP's case, I would prefer using it over hand-rolling my own...Hi
Wow, no problems with PoCo::Server::SOAP?
/me is shocked!
AFAICT: No.
The server is answering on the designated port. I can use SOAP::Lite's method SOAP::Data->name to get me some nice names for the parameters. It does transfer arrays, hashes and scalars without any problem - at least I haven't met any yet.
I didn't benchmarks this, and I have a feeling that using SOAP may not be the most efficient way to transfer data. But it's a trade off against using standard components and protocols. I believe it's worth it.
But, if the other end is a perl application, you could always use POE::Filter::Reference to send pure perl stuff down the pipe, I've used this sometimes when going full-blown SOAP/(Insert toolkit here) would be too much...
Oh, I'm thinking of adding WSDL support to Server::SOAP someday, once I finish my other gazillion projects or somehow find Server::SOAP interesting again =]
-- Apocalypse
Homepage: http://JiNxEdStAr.0ne.us IRC: [EMAIL PROTECTED] IRC: [EMAIL PROTECTED] Perl Stuff: http://search.cpan.org/~APOCAL/
