[29541] in Perl-Users-Digest
Perl-Users Digest, Issue: 785 Volume: 11
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Thu Aug 23 03:09:37 2007
Date: Thu, 23 Aug 2007 00:09:04 -0700 (PDT)
From: Perl-Users Digest <Perl-Users-Request@ruby.OCE.ORST.EDU>
To: Perl-Users@ruby.OCE.ORST.EDU (Perl-Users Digest)
Perl-Users Digest Thu, 23 Aug 2007 Volume: 11 Number: 785
Today's topics:
new CPAN modules on Thu Aug 23 2007 (Randal Schwartz)
Posting Guidelines for comp.lang.perl.misc ($Revision: tadmc@seesig.invalid
Re: Starting with SOAP <jgibson@mail.arc.nasa.gov>
Re: Starting with SOAP <perl4hire@softouch.on.ca>
Re: Starting with SOAP <tadmc@seesig.invalid>
Re: Starting with SOAP xhoster@gmail.com
Re: Stumped: returning a read pipe from a function anno4000@radom.zrz.tu-berlin.de
Re: Symrefs <stoupa@practisoft.cz>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Thu, 23 Aug 2007 04:42:13 GMT
From: merlyn@stonehenge.com (Randal Schwartz)
Subject: new CPAN modules on Thu Aug 23 2007
Message-Id: <Jn7MED.180r@zorch.sf-bay.org>
The following modules have recently been added to or updated in the
Comprehensive Perl Archive Network (CPAN). You can install them using the
instructions in the 'perlmodinstall' page included with your Perl
distribution.
Bricklayer-Templater-0.9.4_with_makefile_this_time
http://search.cpan.org/~zaphar/Bricklayer-Templater-0.9.4_with_makefile_this_time/
yet another templating system. Pure perl, highly flexible with very few dependencies.
----
Business-KontoCheck-2.2
http://search.cpan.org/~michel/Business-KontoCheck-2.2/
Perl extension for checking German and Austrian Bank Account Numbers
----
Cache-FastMmap-1.19
http://search.cpan.org/~robm/Cache-FastMmap-1.19/
Uses an mmap'ed file to act as a shared memory interprocess cache
----
Catalyst-Controller-HTML-FormFu-0.01001
http://search.cpan.org/~cfranks/Catalyst-Controller-HTML-FormFu-0.01001/
----
Catalyst-Runtime-5.7010
http://search.cpan.org/~mramberg/Catalyst-Runtime-5.7010/
Catalyst Runtime version
----
Catalyst-View-BK-0.1_with_makefile_this_time
http://search.cpan.org/~zaphar/Catalyst-View-BK-0.1_with_makefile_this_time/
Catalyst View for Bricklayer::Templater
----
Catalyst-View-Email-0.06
http://search.cpan.org/~jshirley/Catalyst-View-Email-0.06/
Send Email from Catalyst
----
Crypt-KDF-0.02
http://search.cpan.org/~areibens/Crypt-KDF-0.02/
----
DBI-1.59_1
http://search.cpan.org/~timb/DBI-1.59_1/
Database independent interface for Perl
----
DBIx-Class-HTML-FormFu-0.01001
http://search.cpan.org/~cfranks/DBIx-Class-HTML-FormFu-0.01001/
Fill a HTML::FormFu form from the database and vice-versa
----
Data-Dump-Streamer-2.04-34
http://search.cpan.org/~yves/Data-Dump-Streamer-2.04-34/
Accurately serialize a data structure as Perl code.
----
Data-Dump-Streamer-2.05-36
http://search.cpan.org/~yves/Data-Dump-Streamer-2.05-36/
Accurately serialize a data structure as Perl code.
----
Finance-Bank-Postbank_de-0.26
http://search.cpan.org/~corion/Finance-Bank-Postbank_de-0.26/
Check your Postbank.de bank account from Perl
----
Games-Tournament-Swiss-0.05
http://search.cpan.org/~drbean/Games-Tournament-Swiss-0.05/
FIDE Swiss Same-Rank Contestant Pairing
----
GoferTransport-http-1.012
http://search.cpan.org/~timb/GoferTransport-http-1.012/
----
HTML-FormFu-0.01001
http://search.cpan.org/~cfranks/HTML-FormFu-0.01001/
HTML Form Creation, Rendering and Validation Framework
----
HTML-FormFu-0.01002
http://search.cpan.org/~cfranks/HTML-FormFu-0.01002/
HTML Form Creation, Rendering and Validation Framework
----
HTML-FormFu-0.01003
http://search.cpan.org/~cfranks/HTML-FormFu-0.01003/
HTML Form Creation, Rendering and Validation Framework
----
HTML-FormFu-Imager-0.01001
http://search.cpan.org/~cfranks/HTML-FormFu-Imager-0.01001/
Imager.pm helpers for HTML::FormFu file uploads
----
HTML-Menu-TreeView-0.7.6
http://search.cpan.org/~lze/HTML-Menu-TreeView-0.7.6/
----
Handel-1.00005
http://search.cpan.org/~claco/Handel-1.00005/
A cart/order/checkout framework with AxKit/TT/Catalyst support
----
IPA-1.04
http://search.cpan.org/~karasik/IPA-1.04/
Image Processing Algorithms
----
LEGO-Colors-0.3
http://search.cpan.org/~avif/LEGO-Colors-0.3/
Set of LEGO Color data
----
LEGO-Colors-0.3.1
http://search.cpan.org/~avif/LEGO-Colors-0.3.1/
Set of LEGO Color data
----
LEOCHARRE-DEBUG-1.02
http://search.cpan.org/~leocharre/LEOCHARRE-DEBUG-1.02/
my default debug subroutines
----
Lingua-EN-Titlecase-0.06
http://search.cpan.org/~ashley/Lingua-EN-Titlecase-0.06/
Titlecasing of English words by traditional editorial rules.
----
List-Tuples-0.01
http://search.cpan.org/~nkh/List-Tuples-0.01/
Makes tuples from lists
----
MOSES-MOBY-0.80
http://search.cpan.org/~ekawas/MOSES-MOBY-0.80/
Perl extension for the automatic generation of BioMOBY web services
----
MOSES-MOBY-0.81
http://search.cpan.org/~ekawas/MOSES-MOBY-0.81/
Perl extension for the automatic generation of BioMOBY web services
----
Mail-Postini-0.11
http://search.cpan.org/~scottw/Mail-Postini-0.11/
Perl extension for talking to Postini
----
Mail-Postini-0.12
http://search.cpan.org/~scottw/Mail-Postini-0.12/
Perl extension for talking to Postini
----
Money-ChangeMaker-0.3
http://search.cpan.org/~avif/Money-ChangeMaker-0.3/
A module to make change based on a monetary quantity.
----
Money-ChangeMaker-0.3.1
http://search.cpan.org/~avif/Money-ChangeMaker-0.3.1/
A module to make change based on a monetary quantity.
----
OCR-Naive-0.02
http://search.cpan.org/~karasik/OCR-Naive-0.02/
convert images into text in a extremely naive fashion
----
PDFLib-PPS-0.01
http://search.cpan.org/~montuori/PDFLib-PPS-0.01/
PDFLib Personalization Server OO Interface
----
QWizard-3.07
http://search.cpan.org/~hardaker/QWizard-3.07/
Display a series of questions, get the answers, and act on the answers.
----
SMS-AQL-0.06
http://search.cpan.org/~bigpresh/SMS-AQL-0.06/
Perl extension to send SMS text messages via AQ's SMS service
----
Socket-Class-1.0.1
http://search.cpan.org/~chrmue/Socket-Class-1.0.1/
A class to communicate with sockets
----
Socket-Class-1.0.2
http://search.cpan.org/~chrmue/Socket-Class-1.0.2/
A class to communicate with sockets
----
Socket-Class-1.0.3
http://search.cpan.org/~chrmue/Socket-Class-1.0.3/
A class to communicate with sockets
----
Term-Menus-1.21
http://search.cpan.org/~reedfish/Term-Menus-1.21/
Create Powerful Terminal, Console and CMD Enviroment Menus
----
Text-Positional-Ngram-0.4
http://search.cpan.org/~btmcinnes/Text-Positional-Ngram-0.4/
----
URI-chrome-0.01
http://search.cpan.org/~zigorou/URI-chrome-0.01/
Mozilla chrome uri
----
UWO-Student-0.01a
http://search.cpan.org/~frequency/UWO-Student-0.01a/
Provides Perl object representation of a University of Western Ontario student.
----
WWW-Patent-Page-0.101.0
http://search.cpan.org/~anonwb/WWW-Patent-Page-0.101.0/
get a patent page or document (e.g. htm, pdf, tif) from selected source (e.g. from United States Patent and Trademark Office (USPTO) website or the European Patent Office (ESPACE_EP). and place into a
----
WWW-Vox-1.1
http://search.cpan.org/~markpasc/WWW-Vox-1.1/
Interact programmatically with Vox
----
WebService-Recruit-HotPepper-0.03
http://search.cpan.org/~bashi/WebService-Recruit-HotPepper-0.03/
perl interface for HotPepper Web Service
----
parrot-0.4.15
http://search.cpan.org/~pmic/parrot-0.4.15/
If you're an author of one of these modules, please submit a detailed
announcement to comp.lang.perl.announce, and we'll pass it along.
This message was generated by a Perl program described in my Linux
Magazine column, which can be found on-line (along with more than
200 other freely available past column articles) at
http://www.stonehenge.com/merlyn/LinuxMag/col82.html
print "Just another Perl hacker," # the original
--
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
<merlyn@stonehenge.com> <URL:http://www.stonehenge.com/merlyn/>
Perl/Unix/security consulting, Technical writing, Comedy, etc. etc.
See PerlTraining.Stonehenge.com for onsite and open-enrollment Perl training!
------------------------------
Date: Wed, 22 Aug 2007 23:24:10 GMT
From: tadmc@seesig.invalid
Subject: Posting Guidelines for comp.lang.perl.misc ($Revision: 1.8 $)
Message-Id: <uA3zi.4130$Oo.3745@newssvr17.news.prodigy.net>
Outline
Before posting to comp.lang.perl.misc
Must
- Check the Perl Frequently Asked Questions (FAQ)
- Check the other standard Perl docs (*.pod)
Really Really Should
- Lurk for a while before posting
- Search a Usenet archive
If You Like
- Check Other Resources
Posting to comp.lang.perl.misc
Is there a better place to ask your question?
- Question should be about Perl, not about the application area
How to participate (post) in the clpmisc community
- Carefully choose the contents of your Subject header
- Use an effective followup style
- Speak Perl rather than English, when possible
- Ask perl to help you
- Do not re-type Perl code
- Provide enough information
- Do not provide too much information
- Do not post binaries, HTML, or MIME
Social faux pas to avoid
- Asking a Frequently Asked Question
- Asking a question easily answered by a cursory doc search
- Asking for emailed answers
- Beware of saying "doesn't work"
- Sending a "stealth" Cc copy
Be extra cautious when you get upset
- Count to ten before composing a followup when you are upset
- Count to ten after composing and before posting when you are upset
-----------------------------------------------------------------
Posting Guidelines for comp.lang.perl.misc ($Revision: 1.8 $)
This newsgroup, commonly called clpmisc, is a technical newsgroup
intended to be used for discussion of Perl related issues (except job
postings), whether it be comments or questions.
As you would expect, clpmisc discussions are usually very technical in
nature and there are conventions for conduct in technical newsgroups
going somewhat beyond those in non-technical newsgroups.
The article at:
http://www.catb.org/~esr/faqs/smart-questions.html
describes how to get answers from technical people in general.
This article describes things that you should, and should not, do to
increase your chances of getting an answer to your Perl question. It is
available in POD, HTML and plain text formats at:
http://www.rehabitation.com/clpmisc.shtml
For more information about netiquette in general, see the "Netiquette
Guidelines" at:
http://andrew2.andrew.cmu.edu/rfc/rfc1855.html
A note to newsgroup "regulars":
Do not use these guidelines as a "license to flame" or other
meanness. It is possible that a poster is unaware of things
discussed here. Give them the benefit of the doubt, and just
help them learn how to post, rather than assume that they do
know and are being the "bad kind" of Lazy.
A note about technical terms used here:
In this document, we use words like "must" and "should" as
they're used in technical conversation (such as you will
encounter in this newsgroup). When we say that you *must* do
something, we mean that if you don't do that something, then
it's unlikely that you will benefit much from this group.
We're not bossing you around; we're making the point without
lots of words.
Do *NOT* send email to the maintainer of these guidelines. It will be
discarded unread. The guidelines belong to the newsgroup so all
discussion should appear in the newsgroup. I am just the secretary that
writes down the consensus of the group.
Before posting to comp.lang.perl.misc
Must
This section describes things that you *must* do before posting to
clpmisc, in order to maximize your chances of getting meaningful replies
to your inquiry and to avoid getting flamed for being lazy and trying to
have others do your work.
The perl distribution includes documentation that is copied to your hard
drive when you install perl. Also installed is a program for looking
things up in that (and other) documentation named 'perldoc'.
You should either find out where the docs got installed on your system,
or use perldoc to find them for you. Type "perldoc perldoc" to learn how
to use perldoc itself. Type "perldoc perl" to start reading Perl's
standard documentation.
Check the Perl Frequently Asked Questions (FAQ)
Checking the FAQ before posting is required in Big 8 newsgroups in
general, there is nothing clpmisc-specific about this requirement.
You are expected to do this in nearly all newsgroups.
You can use the "-q" switch with perldoc to do a word search of the
questions in the Perl FAQs.
Check the other standard Perl docs (*.pod)
The perl distribution comes with much more documentation than is
available for most other newsgroups, so in clpmisc you should also
see if you can find an answer in the other (non-FAQ) standard docs
before posting.
It is *not* required, or even expected, that you actually *read* all of
Perl's standard docs, only that you spend a few minutes searching them
before posting.
Try doing a word-search in the standard docs for some words/phrases
taken from your problem statement or from your very carefully worded
"Subject:" header.
Really Really Should
This section describes things that you *really should* do before posting
to clpmisc.
Lurk for a while before posting
This is very important and expected in all newsgroups. Lurking means
to monitor a newsgroup for a period to become familiar with local
customs. Each newsgroup has specific customs and rituals. Knowing
these before you participate will help avoid embarrassing social
situations. Consider yourself to be a foreigner at first!
Search a Usenet archive
There are tens of thousands of Perl programmers. It is very likely
that your question has already been asked (and answered). See if you
can find where it has already been answered.
One such searchable archive is:
http://groups.google.com/advanced_group_search
If You Like
This section describes things that you *can* do before posting to
clpmisc.
Check Other Resources
You may want to check in books or on web sites to see if you can
find the answer to your question.
But you need to consider the source of such information: there are a
lot of very poor Perl books and web sites, and several good ones
too, of course.
Posting to comp.lang.perl.misc
There can be 200 messages in clpmisc in a single day. Nobody is going to
read every article. They must decide somehow which articles they are
going to read, and which they will skip.
Your post is in competition with 199 other posts. You need to "win"
before a person who can help you will even read your question.
These sections describe how you can help keep your article from being
one of the "skipped" ones.
Is there a better place to ask your question?
Question should be about Perl, not about the application area
It can be difficult to separate out where your problem really is,
but you should make a conscious effort to post to the most
applicable newsgroup. That is, after all, where you are the most
likely to find the people who know how to answer your question.
Being able to "partition" a problem is an essential skill for
effectively troubleshooting programming problems. If you don't get
that right, you end up looking for answers in the wrong places.
It should be understood that you may not know that the root of your
problem is not Perl-related (the two most frequent ones are CGI and
Operating System related), so off-topic postings will happen from
time to time. Be gracious when someone helps you find a better place
to ask your question by pointing you to a more applicable newsgroup.
How to participate (post) in the clpmisc community
Carefully choose the contents of your Subject header
You have 40 precious characters of Subject to win out and be one of
the posts that gets read. Don't waste them. Take care while
composing them, they are the key that opens the door to getting an
answer.
Spend them indicating what aspect of Perl others will find if they
should decide to read your article.
Do not spend them indicating "experience level" (guru, newbie...).
Do not spend them pleading (please read, urgent, help!...).
Do not spend them on non-Subjects (Perl question, one-word
Subject...)
For more information on choosing a Subject see "Choosing Good
Subject Lines":
http://www.cpan.org/authors/id/D/DM/DMR/subjects.post
Part of the beauty of newsgroup dynamics, is that you can contribute
to the community with your very first post! If your choice of
Subject leads a fellow Perler to find the thread you are starting,
then even asking a question helps us all.
Use an effective followup style
When composing a followup, quote only enough text to establish the
context for the comments that you will add. Always indicate who
wrote the quoted material. Never quote an entire article. Never
quote a .signature (unless that is what you are commenting on).
Intersperse your comments *following* each section of quoted text to
which they relate. Unappreciated followup styles are referred to as
"top-posting", "Jeopardy" (because the answer comes before the
question), or "TOFU" (Text Over, Fullquote Under).
Reversing the chronology of the dialog makes it much harder to
understand (some folks won't even read it if written in that style).
For more information on quoting style, see:
http://web.presby.edu/~nnqadmin/nnq/nquote.html
Speak Perl rather than English, when possible
Perl is much more precise than natural language. Saying it in Perl
instead will avoid misunderstanding your question or problem.
Do not say: I have variable with "foo\tbar" in it.
Instead say: I have $var = "foo\tbar", or I have $var = 'foo\tbar',
or I have $var = <DATA> (and show the data line).
Ask perl to help you
You can ask perl itself to help you find common programming mistakes
by doing two things: enable warnings (perldoc warnings) and enable
"strict"ures (perldoc strict).
You should not bother the hundreds/thousands of readers of the
newsgroup without first seeing if a machine can help you find your
problem. It is demeaning to be asked to do the work of a machine. It
will annoy the readers of your article.
You can look up any of the messages that perl might issue to find
out what the message means and how to resolve the potential mistake
(perldoc perldiag). If you would like perl to look them up for you,
you can put "use diagnostics;" near the top of your program.
Do not re-type Perl code
Use copy/paste or your editor's "import" function rather than
attempting to type in your code. If you make a typo you will get
followups about your typos instead of about the question you are
trying to get answered.
Provide enough information
If you do the things in this item, you will have an Extremely Good
chance of getting people to try and help you with your problem!
These features are a really big bonus toward your question winning
out over all of the other posts that you are competing with.
First make a short (less than 20-30 lines) and *complete* program
that illustrates the problem you are having. People should be able
to run your program by copy/pasting the code from your article. (You
will find that doing this step very often reveals your problem
directly. Leading to an answer much more quickly and reliably than
posting to Usenet.)
Describe *precisely* the input to your program. Also provide example
input data for your program. If you need to show file input, use the
__DATA__ token (perldata.pod) to provide the file contents inside of
your Perl program.
Show the output (including the verbatim text of any messages) of
your program.
Describe how you want the output to be different from what you are
getting.
If you have no idea at all of how to code up your situation, be sure
to at least describe the 2 things that you *do* know: input and
desired output.
Do not provide too much information
Do not just post your entire program for debugging. Most especially
do not post someone *else's* entire program.
Do not post binaries, HTML, or MIME
clpmisc is a text only newsgroup. If you have images or binaries
that explain your question, put them in a publically accessible
place (like a Web server) and provide a pointer to that location. If
you include code, cut and paste it directly in the message body.
Don't attach anything to the message. Don't post vcards or HTML.
Many people (and even some Usenet servers) will automatically filter
out such messages. Many people will not be able to easily read your
post. Plain text is something everyone can read.
Social faux pas to avoid
The first two below are symptoms of lots of FAQ asking here in clpmisc.
It happens so often that folks will assume that it is happening yet
again. If you have looked but not found, or found but didn't understand
the docs, say so in your article.
Asking a Frequently Asked Question
It should be understood that you may have missed the applicable FAQ
when you checked, which is not a big deal. But if the Frequently
Asked Question is worded similar to your question, folks will assume
that you did not look at all. Don't become indignant at pointers to
the FAQ, particularly if it solves your problem.
Asking a question easily answered by a cursory doc search
If folks think you have not even tried the obvious step of reading
the docs applicable to your problem, they are likely to become
annoyed.
If you are flamed for not checking when you *did* check, then just
shrug it off (and take the answer that you got).
Asking for emailed answers
Emailed answers benefit one person. Posted answers benefit the
entire community. If folks can take the time to answer your
question, then you can take the time to go get the answer in the
same place where you asked the question.
It is OK to ask for a *copy* of the answer to be emailed, but many
will ignore such requests anyway. If you munge your address, you
should never expect (or ask) to get email in response to a Usenet
post.
Ask the question here, get the answer here (maybe).
Beware of saying "doesn't work"
This is a "red flag" phrase. If you find yourself writing that,
pause and see if you can't describe what is not working without
saying "doesn't work". That is, describe how it is not what you
want.
Sending a "stealth" Cc copy
A "stealth Cc" is when you both email and post a reply without
indicating *in the body* that you are doing so.
Be extra cautious when you get upset
Count to ten before composing a followup when you are upset
This is recommended in all Usenet newsgroups. Here in clpmisc, most
flaming sub-threads are not about any feature of Perl at all! They
are most often for what was seen as a breach of netiquette. If you
have lurked for a bit, then you will know what is expected and won't
make such posts in the first place.
But if you get upset, wait a while before writing your followup. I
recommend waiting at least 30 minutes.
Count to ten after composing and before posting when you are upset
After you have written your followup, wait *another* 30 minutes
before committing yourself by posting it. You cannot take it back
once it has been said.
AUTHOR
Tad McClellan and many others on the comp.lang.perl.misc newsgroup.
--
Tad McClellan
email: perl -le "print scalar reverse qq/moc.noitatibaher\100cmdat/"
------------------------------
Date: Wed, 22 Aug 2007 16:43:36 -0700
From: Jim Gibson <jgibson@mail.arc.nasa.gov>
Subject: Re: Starting with SOAP
Message-Id: <220820071643361075%jgibson@mail.arc.nasa.gov>
In article <46CCAE30.3000100@softouch.on.ca>, Amer Neely
<perl4hire@softouch.on.ca> wrote:
>
> I have managed to get some headway on some test scripts. But an error
> message is confusing me.
>
> The server code:
> #! /usr/bin/perl
> ## test using SOAP to display values from another script
>
> BEGIN
> {
> open (STDERR,">>$0-err.txt");
> print STDERR "\n",scalar localtime,"\n";
> }
>
> use strict;
> use warnings;
>
> use lib '/home/softouch/public_html/cgi-bin/PerlMods/SOAP-0.28/blib/lib';
> use SOAP::Transport::HTTP;
> SOAP::Transport::HTTP::CGI
> -> dispatch_to('ShowMe')
> -> handle;
...
>
> The error:
> Can't locate SOAP/Transport/HTTP.pm in @INC (@INC contains:
> /home/softouch/public_html/cgi-bin/PerlMods/SOAP-0.28/blib/lib
...
>
> It seems that it is looking for HTTP.pm, but HTTP is a directory under
> SOAP/Transport. CGI.pm is in the HTTP directory.
>
> This is modified from a script in the SOAP::Lite distribution.
It looks like you didn't install the SOAP::Transport::HTTP module,
which should be installed as .../SOAP/Transport/HTTP.pm.
The HTTP directory in .../SOAP/Transport will be the home of modules
such as SOAP::Transport::HTTP::CGI.
Because of Perl's naming convention for modules, is possible and common
for module XXX.pm and directory XXX to exist in the same directory.
--
Jim Gibson
Posted Via Usenet.com Premium Usenet Newsgroup Services
----------------------------------------------------------
** SPEED ** RETENTION ** COMPLETION ** ANONYMITY **
----------------------------------------------------------
http://www.usenet.com
------------------------------
Date: Wed, 22 Aug 2007 21:05:44 -0400
From: Amer Neely <perl4hire@softouch.on.ca>
Subject: Re: Starting with SOAP
Message-Id: <925zi.487$k22.205@read2.cgocable.net>
Jim Gibson wrote:
> In article <46CCAE30.3000100@softouch.on.ca>, Amer Neely
> <perl4hire@softouch.on.ca> wrote:
>
>
>> I have managed to get some headway on some test scripts. But an error
>> message is confusing me.
>>
>> The server code:
>> #! /usr/bin/perl
>> ## test using SOAP to display values from another script
>>
>> BEGIN
>> {
>> open (STDERR,">>$0-err.txt");
>> print STDERR "\n",scalar localtime,"\n";
>> }
>>
>> use strict;
>> use warnings;
>>
>> use lib '/home/softouch/public_html/cgi-bin/PerlMods/SOAP-0.28/blib/lib';
>> use SOAP::Transport::HTTP;
>> SOAP::Transport::HTTP::CGI
>> -> dispatch_to('ShowMe')
>> -> handle;
> ...
>
>
>> The error:
>> Can't locate SOAP/Transport/HTTP.pm in @INC (@INC contains:
>> /home/softouch/public_html/cgi-bin/PerlMods/SOAP-0.28/blib/lib
> ...
>
>> It seems that it is looking for HTTP.pm, but HTTP is a directory under
>> SOAP/Transport. CGI.pm is in the HTTP directory.
>>
>> This is modified from a script in the SOAP::Lite distribution.
>
> It looks like you didn't install the SOAP::Transport::HTTP module,
> which should be installed as .../SOAP/Transport/HTTP.pm.
>
> The HTTP directory in .../SOAP/Transport will be the home of modules
> such as SOAP::Transport::HTTP::CGI.
>
> Because of Perl's naming convention for modules, is possible and common
> for module XXX.pm and directory XXX to exist in the same directory.
>
Arghh. I was under the impression that the double-colons '::' were
directory delimiters. So the line
use SOAP::Transport::HTTP;
should be looking for SOAP/Transport/HTTP, which holds the CGI.pm module.
When I do a search for 'soap::transport::http' at CPAN I get a list, and
the first hit, SOAP::Transport::HTTP, takes me to 'SOAP-Lite-0.69'. The
documentation leads me to believe that SOAP::Transport::HTTP is included
in SOAP-Lite-0.69.
Obviously I'm way off track in my belief system. This is one of the more
confusing things I find about Perl.
--
Amer Neely
w: www.webmechanic.softouch.on.ca/
Perl | MySQL programming for all data entry forms.
"Others make web sites. We make web sites work!"
------------------------------
Date: Wed, 22 Aug 2007 22:03:59 -0500
From: Tad McClellan <tadmc@seesig.invalid>
Subject: Re: Starting with SOAP
Message-Id: <slrnfcpu8v.8ss.tadmc@tadmc30.sbcglobal.net>
Amer Neely <perl4hire@softouch.on.ca> wrote:
> I was under the impression that the double-colons '::' were
> directory delimiters.
They are.
errr, almost.
Double colons are directory _separators_.
A "delimiter" goes on both ends (it marks the "limits"),
a "separator" goes between things.
> So the line
> use SOAP::Transport::HTTP;
> should be looking for SOAP/Transport/HTTP,
No, it is looking for a _file_ (named .../SOAP/Transport/HTTP.pm)
not a directory.
--
Tad McClellan
email: perl -le "print scalar reverse qq/moc.noitatibaher\100cmdat/"
------------------------------
Date: 23 Aug 2007 04:14:12 GMT
From: xhoster@gmail.com
Subject: Re: Starting with SOAP
Message-Id: <20070823001416.836$fb@newsreader.com>
Amer Neely <perl4hire@softouch.on.ca> wrote:
> xhoster@gmail.com wrote:
> > Amer Neely <perl4hire@softouch.on.ca> wrote:
> >> I need to update a script on one server with data from a form on
> >> another server. It has been suggested that SOAP would work for this.
> >> I've never used SOAP, and am overwhelmed with the number of 'SOAP*'
> >> modules on CPAN. I've read that perhaps I should use a language with
> >> better support for SOAP (PHP ?) but the existing script is in Perl and
> >> I'd prefer to stick with that if possible.
> >
> > It sounds like the tail is wagging the dog. For one thing, you
> > probably shouldn't update scripts based on form submissions. Why not
> > update some database that the script accesses? That would probably
> > solve the problem right there. But if you want Perl script-to-Perl
> > script communication, pick a protocol that Perl is good at, rather than
> > picking a random protocol and then figure out to implement in Perl.
> >
> > Xho
> >
>
> Sounds like good advice. However the 'other script' is not in my
> control, and I'm not even sure it is Perl - likely PHP. The owner is the
> one looking for a SOAP solution. They are asking for an XML document of
> the form data.
I'm still not sure I follow. You own one part and not the other part, and
you want your part to be in Perl. But would your part be the SOAP client
or the SOAP server? And what is this "form" data, is it a CGI form? And
is that coming from the other party, or is their a third party submitting
the form, which you are supposed to do convert into SOAP and pass it along?
> At present the form data is not being saved in a database, so that is
> not an immediate solution, although I could present that to my client
> and the 3rd party.
If the form isn't in soapy XML, and that is what they want it in, then
just saving the form as is in a database isn't going to help. But anyway,
I think there was miscommunication. You don't want to update a script
(i.e. change the source code of a script) on another server, you just
want to interact with a script on another server, right? If so, then
you might want to ask "What changes would your script make to the database
if my script called your script the way you want it to? Why not just
let me make those changes myself?" Unfortunately, many people think
that the "right" way to do things is to treat the database just as some
opaque bit-bucket and the "real" data lives in some XML-object model and
therefore can't be assessed directly in the database. These people are
almost always wrong, but sometimes they are the ones signing the
paycheck.
<snip errors>
I think the module finding problems have already been addressed, but
just a word of caution. Just because you can make a client and a
server, both from Perl using SOAP::Lite, that will work with each other
doesn't mean much. It doesn't mean the client will work with another
language's server, or the server will work with another language's client.
Xho
--
-------------------- http://NewsReader.Com/ --------------------
Usenet Newsgroup Service $9.95/Month 30GB
------------------------------
Date: 23 Aug 2007 07:08:20 GMT
From: anno4000@radom.zrz.tu-berlin.de
Subject: Re: Stumped: returning a read pipe from a function
Message-Id: <5j4q34F3rd61eU1@mid.dfncis.de>
<xhoster@gmail.com> wrote in comp.lang.perl.misc:
> anno4000@radom.zrz.tu-berlin.de wrote:
> > <xhoster@gmail.com> wrote in comp.lang.perl.misc:
> >
> > [...]
> >
> > > Hmm. That makes me wonder, when you do an ordinary pipe open
> > > (not IPC::Open? open), the corresponding close automatically waits on
> > > the child. How does it know what pid to wait on?
> >
> > It has been my understanding that close() waits for one child to finish,
> > never mind the PID.
[...]
> I just looked at the source for 5.8.7. It seems to store the pid in
> some secret array, with the fd as the index.
Ah, that makes sense. Thanks for the correction.
Anno
------------------------------
Date: Thu, 23 Aug 2007 03:27:00 +0200
From: "Petr Vileta" <stoupa@practisoft.cz>
Subject: Re: Symrefs
Message-Id: <faio1m$1moa$1@ns.felk.cvut.cz>
Jürgen Exner wrote:
> Petr Vileta wrote:
>> Jürgen Exner wrote:
>>> Petr Vileta wrote:
>>>> http://www.france-weather.fr?town=Paris
>>>> http://www.france-weather.fr?town=Caen
>
> Don't you think that in particular in a case like this an additional
> abstraction layer would be very convenient?
> Then the person who enters the data in the DB can use a meaningful
> name without the need to know how the subs are named in your program.
>
Person store links to DB via web form (password protected) and the sub name
is auto-generated from URL.
Say, for example above, the generated sub name will be
"www_france__weather_fr" and of course this name is checked for existence
elsewhere in the DB.
Person can add many of the similar links to DB and if the sub exist then I
have no job ;-) If somebody add a new server (unknown in DB) then I get
email report about non-existing sub and I write it.
>> When the sub name will be say 8 characters only + 2 characters =>
>> then it means 40000 characters of needless code.
>
> How many characters to you expect your subs to be on average? Maybe
> 15 lines of 30 characters each (just a guess, but I think in reality
> it will be significantly larger)? Then we are talking about an
> increase in code size of less than 3%.
I prefer code with self-checking and self-learning functions. Yes, this case
is not "artificial intelligence" but allow to people work with minimal
efforts. I started my programming on control systems in assembler and this
practices was be usual. Self -checking, -learnign, -modifying programs.
--
Petr Vileta, Czech republic
(My server rejects all messages from Yahoo and Hotmail. Send me your mail
from another non-spammer site please.)
------------------------------
Date: 6 Apr 2001 21:33:47 GMT (Last modified)
From: Perl-Users-Request@ruby.oce.orst.edu (Perl-Users-Digest Admin)
Subject: Digest Administrivia (Last modified: 6 Apr 01)
Message-Id: <null>
Administrivia:
#The Perl-Users Digest is a retransmission of the USENET newsgroup
#comp.lang.perl.misc. For subscription or unsubscription requests, send
#the single line:
#
# subscribe perl-users
#or:
# unsubscribe perl-users
#
#to almanac@ruby.oce.orst.edu.
NOTE: due to the current flood of worm email banging on ruby, the smtp
server on ruby has been shut off until further notice.
To submit articles to comp.lang.perl.announce, send your article to
clpa@perl.com.
#To request back copies (available for a week or so), send your request
#to almanac@ruby.oce.orst.edu with the command "send perl-users x.y",
#where x is the volume number and y is the issue number.
#For other requests pertaining to the digest, send mail to
#perl-users-request@ruby.oce.orst.edu. Do not waste your time or mine
#sending perl questions to the -request address, I don't have time to
#answer them even if I did know the answer.
------------------------------
End of Perl-Users Digest V11 Issue 785
**************************************
