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.
  • I don't think that 3 paragraphs really says how it was done or what was accomplished. Was he using server side or client side SOAP::Lite? Was he using SOAP::HTTP::Daemon or an apache frontend? These are the things that will help get SOAP::Lite in the workplace.
    • Was he using server side or client side SOAP::Lite?
      I used it both server-side (Windows NT) and client-side (Solaris).

      Was he using SOAP::HTTP::Daemon or an apache frontend?
      I used SOAP::Transport::HTTP::CGI.

      I needed to write a CGI script that integrated data from an Informix database on a Solaris box with data from a SQL Server database on an NT box. I first tried to serve the script on the NT box and connect to Informix remotely with DBD::Informix. We ran into a lot of problems installing DBD::Informix on NT and time was a critical issue.

      Since I had used the SOAP::Lite distribution on another project (PGAS [sourceforge.net]), I thought it could be a good solution here. Since SOAP::Lite comes standard with ActivePerl (installed on the NT box), we only needed to install the module on the Solaris box. A few lines of code later and we were up and running with the CGI being served on the Solaris box, making SOAP calls to a CGI-based SOAP server on the NT box.

      If you want more details, let me know.

      --Dave