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.
  • Hmm. Now to rewrite WWW::UsePerl::Journal to make use of SOAP.

    How does one get the recent journals via RSS anyway? Last time I looked it returned invalid URLs in the RSS.
    --
      ---ict / Spoon
    • You'll want to be careful in how you handle the checking for SOAP at build-time and run-time. Don't want to force people into installing something, better to give them the choice. Unless they already have it installed, of course :-).

      --rjray

      --

      --rjray

      • Hmm. I'm more of the philosophy: why have two versions of the same code?

        At the very least, the more modules that make people have SOAP client software, then the more SOAP server software there can be.

        That said, is SOAP::Lite that difficult to install?
        --
          ---ict / Spoon
        • If you're talking about using SOAP versus trying to read, parse, and post data by emulating a web client, there's no contest: use SOAP. The web client interface is guaranteed to change some day in subtle ways that will break any code you have. The SOAP interface is not. I won't say it's guaranteed to not change, but I'll try not to change it. :-)

          So yeah, if it were me, I would require users to use SOAP::Lite, or some other SOAP client module.