NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.
All the Perl that's Practical to Extract and Report
I pour the blue liquid on the red liquid. If it doesn't blow up on my
face, I proceed to turn up the flame under the blue liquid, and so on.
I have very little idea of what I am really doing, I just like the
pretty colors :-)
-- Jarkko Hietaniemi
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
uh? SOAP is not IIOP! (Score:2)
If you want to move complex XML data with SOAP, use xlink and attached a (preferably suitably compressed and then encoded) MIME attachment.
You should be using SOAP to access and run methods on objects at the server, possibly passing small simple objects or data as arguments.
@JAPH = qw(Hacker Perl Another Just);
print reverse @JAPH;
Re:uh? SOAP is not IIOP! (Score:1)
Having said that it could well be the best tech for the job, and I'm not so biased that I wouldn't contemplate a bit of CORBA on my CV if it was the right way to go, but I would have to overcome the hurdles associated with the perceived misconceptions about it.
So, and purely from a hypothetical PHB angle, I was wondering if you could point me in the direction of some advocacy material, perhaps a couple of tutorials which I could garner proof of concept material from, or similar?
Reply to This
Parent
Re:uh? SOAP is not IIOP! (Score:2)
If you are moving a lot of complex objects around then CORBA is probably a better bet than SOAP.
I was thinking more along the lines of using SOAP better by simplifying what you do with SOAP, this can be done by providing a nice compressed XML file attached to the webmessage and only passing as simple as possible stuff around. The S in SOAP is for Simple a
@JAPH = qw(Hacker Perl Another Just);
print reverse @JAPH;