Stories
Slash Boxes
Comments
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

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • If you want to move objects around the network use CORBA and IIOP.

    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;
    • My opinion of corba is that I've heard of it, but seem to have this idea from somewhere that it's quite complex and unweildy, and building on these prejudices, may well be overkill for the task in hand. I doubt I'm alone in this probable misconception.

      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
      • CORBA is heavyweight development wise, but on-the-wire is faster and lighter once running than parsing and processing or transforming uncompressed XML.

        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 after all.

        If you are investing resources (time/effort/money/cpu/maintainence) into XML marshalling and wasting bandwidth and cpu moving and processing a shedload of complex XML representing complex objects then naturally you are probably better off using a tool designed for the job.

        --

        @JAPH = qw(Hacker Perl Another Just);
        print reverse @JAPH;