[28942] in Perl-Users-Digest
Perl-Users Digest, Issue: 186 Volume: 11
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Fri Mar 2 06:16:53 2007
Date: Fri, 2 Mar 2007 03:14:05 -0800 (PST)
From: Perl-Users Digest <Perl-Users-Request@ruby.OCE.ORST.EDU>
To: Perl-Users@ruby.OCE.ORST.EDU (Perl-Users Digest)
Perl-Users Digest Fri, 2 Mar 2007 Volume: 11 Number: 186
Today's topics:
need help for this project...... <mkakkad@gmail.com>
Re: need help for this project...... krakle@visto.com
new CPAN modules on Fri Mar 2 2007 (Randal Schwartz)
Re: Perl and MySQL krakle@visto.com
Posting Guidelines for comp.lang.perl.misc ($Revision: tadmc@augustmail.com
Re: Q on regex of LWP::Simple data <len@philpot.org>
Re: Q on regex of LWP::Simple data <bigiain@mightymedia.com.au>
SOAP::Lite serializer or version problem <kari.k.saarela@gmail.com>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: 1 Mar 2007 21:19:15 -0800
From: "Mihir" <mkakkad@gmail.com>
Subject: need help for this project......
Message-Id: <1172812754.915418.114330@j27g2000cwj.googlegroups.com>
Hello,
I am new to XML and PERL and I have a few questions the answers to
which I need to complete a project. All your time and effort would be
highly appreciated. I have to make a small HTML page which would take
in as input the state code, of the 50 states belonging to the Unites
States of America. After the user enters the two letter code and
presses the "GO" button, a *.xsd file is parsed to retrieve
information about the entire state name from the two letter code
inputted by the user. The *.xsd file has more than 50 states and the
other states need to be omitted while validation. Then the PERL script
fetches data from the T-Mobile website about the state inputted by the
user and makes an XML file from the fetched data. Thus the PERl script
will scrape data from the T-Mobile web page to an XML file. Till this
point I cannot use any XML parsers or PERL libraries and all this has
to be coded using some other logic. The user should then see another
web page which will have two more links to another pages. One script
should invoke another page which will have 4 drop down menus each of
which will become active one by one using Javascript functions and
then i can retrieve particular information about different places
(e.g. airport, starbucks etc) choosing different locations and
different places from the created XML file. For this part I can use
PERL libararies and PERL DOM. Can someone please help me or guide me
to a tutorial that tells me the following things:
(1) Parse through an xsd file and capture information from it. (e.g.
if user enters "CA" then from xsd file it should make "CA" to
"California" )
(2) After CA changes to California send that information to a T-Mobile
website and fetch all data corresponding to California.
(3) Make an XML file of only the address and phone number tags from
the fetched data.
(4) Tutorials on step 2 and step 3 would be more on Data Scraping...
(5) Make a webpage having 4 drop down menus but only first one active
and the others becoming active after a selection is made in the forst
drop down menu. (implementation usgin JavaScript)
I highly appreciate all your time and help for this question....
Thanks a lot ......
------------------------------
Date: 1 Mar 2007 23:28:08 -0800
From: krakle@visto.com
Subject: Re: need help for this project......
Message-Id: <1172820488.644052.78460@n33g2000cwc.googlegroups.com>
On Mar 1, 11:19 pm, "Mihir" <mkak...@gmail.com> wrote:
> All your time and effort would be
> highly appreciated.
>
> (clip)
>
> (1) Parse through an xsd file and capture information from it. (e.g.
> if user enters "CA" then from xsd file it should make "CA" to
> "California" )
>
> (2) After CA changes to California send that information to a T-Mobile
> website and fetch all data corresponding to California.
>
> (3) Make an XML file of only the address and phone number tags from
> the fetched data.
>
> (4) Tutorials on step 2 and step 3 would be more on Data Scraping...
>
> (5) Make a webpage having 4 drop down menus but only first one active
> and the others becoming active after a selection is made in the forst
> drop down menu. (implementation usgin JavaScript)
>
> I highly appreciate all your time and help for this question....
> Thanks a lot ......
Who hired you? Seriously, it sounds like you have not the slightest
clue what to do. First, HTML is off topic here. JavaScript is too. In
fact, JavaScript in even an HTML newsgroups is off topic. Second, you
accomplish everything you need to do with Perl and a trip to CPAN (no
I didnt spell CSPAN wrong). The rest is using your head and reading
the docs.
Why should anyone here invest the time and effort in to YOUR project?
You want guidance? Here:
http://www.perl.com
http://www.cpan.org
That's all.
------------------------------
Date: Fri, 2 Mar 2007 05:42:08 GMT
From: merlyn@stonehenge.com (Randal Schwartz)
Subject: new CPAN modules on Fri Mar 2 2007
Message-Id: <JE9H68.625@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.
Acme-DRM-0.03
http://search.cpan.org/~bwarden/Acme-DRM-0.03/
Library providing cryptographic capabilities especially suited for Digital Rights Management. Protects against Pirates. May increase global warming. Note: Not guaranteed to protect against Pirates or
----
Archive-Cpio-0.02
http://search.cpan.org/~pixel/Archive-Cpio-0.02/
module for manipulations of cpio archives
----
Business-OnlinePayment-PayflowPro-0.06
http://search.cpan.org/~plobbes/Business-OnlinePayment-PayflowPro-0.06/
Payflow Pro backend for Business::OnlinePayment
----
CPAN-Reporter-0.40
http://search.cpan.org/~dagolden/CPAN-Reporter-0.40/
Provides Test::Reporter support for CPAN.pm
----
Class-Accessor-Named-0.007
http://search.cpan.org/~jesse/Class-Accessor-Named-0.007/
Better profiling output for Class::Accessor
----
Class-Trigger-0.11
http://search.cpan.org/~miyagawa/Class-Trigger-0.11/
Mixin to add / call inheritable triggers
----
Config-JSON-1.0.2
http://search.cpan.org/~rizen/Config-JSON-1.0.2/
A JSON based config file system.
----
Crypt-ECDSA-0.042
http://search.cpan.org/~billh/Crypt-ECDSA-0.042/
Elliptical Cryptography Digital Signature Algorithm
----
DBD-mysql-4.002
http://search.cpan.org/~capttofu/DBD-mysql-4.002/
MySQL driver for the Perl5 Database Interface (DBI)
----
Data-Phrasebook-0.28
http://search.cpan.org/~barbie/Data-Phrasebook-0.28/
Abstract your queries!
----
Data-Phrasebook-Loader-DBI-0.11
http://search.cpan.org/~barbie/Data-Phrasebook-Loader-DBI-0.11/
Absract your phrases with a DBI driver.
----
Data-Phrasebook-Loader-Ini-0.10
http://search.cpan.org/~barbie/Data-Phrasebook-Loader-Ini-0.10/
Absract your phrases with ini files.
----
Data-Phrasebook-Loader-XML-0.12
http://search.cpan.org/~barbie/Data-Phrasebook-Loader-XML-0.12/
Absract your phrases with XML.
----
Data-Phrasebook-Loader-YAML-0.09
http://search.cpan.org/~barbie/Data-Phrasebook-Loader-YAML-0.09/
Absract your phrases with YAML.
----
Data-RuledValidator-0.07
http://search.cpan.org/~ktat/Data-RuledValidator-0.07/
data validator with rule
----
Devel-TrackObjects-0.1
http://search.cpan.org/~sullr/Devel-TrackObjects-0.1/
Track use of objects
----
Devel-TrackObjects-0.2
http://search.cpan.org/~sullr/Devel-TrackObjects-0.2/
Track use of objects
----
Egg-Plugin-SessionKit-0.06
http://search.cpan.org/~lushe/Egg-Plugin-SessionKit-0.06/
Session plugin for Egg.
----
Email-Address-1.886
http://search.cpan.org/~rjbs/Email-Address-1.886/
RFC 2822 Address Parsing and Creation
----
Google-Checkout-1.0.1
http://search.cpan.org/~dzhuo/Google-Checkout-1.0.1/
----
HTML-Widget-1.11
http://search.cpan.org/~cfranks/HTML-Widget-1.11/
HTML Widget And Validation Framework
----
ICS-Simple-0.06
http://search.cpan.org/~wilsond/ICS-Simple-0.06/
Simple interface to CyberSource ICS2
----
IO-Simple-0.03
http://search.cpan.org/~ericjh/IO-Simple-0.03/
Adds object oriented cabalilities to file handles and provides fatal handling.
----
InSilicoSpectro-1.0.10
http://search.cpan.org/~alexmass/InSilicoSpectro-1.0.10/
Open source Perl library for proteomics
----
Lemonldap-Config-Parameters-3.1.0
http://search.cpan.org/~egerman/Lemonldap-Config-Parameters-3.1.0/
Backend of configuration for lemonldap SSO system
----
Lemonldap-Handlers-Generic-3.1.0
http://search.cpan.org/~egerman/Lemonldap-Handlers-Generic-3.1.0/
Perl extension for Lemonldap sso system
----
Lemonldap-Portal-Standard-3.1.0
http://search.cpan.org/~egerman/Lemonldap-Portal-Standard-3.1.0/
Perl extension for the Lemonldap SSO system
----
Log-Handler-0.09
http://search.cpan.org/~bloonix/Log-Handler-0.09/
A simple handler to log messages to log files.
----
Module-Depends-0.12
http://search.cpan.org/~rclamp/Module-Depends-0.12/
identify the dependencies of a distribution
----
Params-Check-0.26
http://search.cpan.org/~kane/Params-Check-0.26/
A generic input parsing/checking mechanism.
----
SVN-Notify-Mirror-0.036
http://search.cpan.org/~jpeacock/SVN-Notify-Mirror-0.036/
Keep a mirrored working copy of a repository path
----
Template-Declare-0.05
http://search.cpan.org/~jesse/Template-Declare-0.05/
Perlish declarative templates
----
Test-Class-0.24
http://search.cpan.org/~adie/Test-Class-0.24/
Easily create test classes in an xUnit/JUnit style
----
Test-YAML-Meta-0.03
http://search.cpan.org/~barbie/Test-YAML-Meta-0.03/
Validation of the META.yml file in a distribution.
----
Text-CSV-LibCSV-0.02
http://search.cpan.org/~jiro/Text-CSV-LibCSV-0.02/
comma-separated values manipulation routines (using libcsv)
----
URI-ParseSearchString-1.9
http://search.cpan.org/~sden/URI-ParseSearchString-1.9/
parse Apache refferer logs and extract search engine query strings.
----
WWW-Scraper-ISBN-ORA_Driver-0.08
http://search.cpan.org/~barbie/WWW-Scraper-ISBN-ORA_Driver-0.08/
Search driver for O'Reilly Media's online catalog.
----
WWW-Scraper-ISBN-Pearson_Driver-0.08
http://search.cpan.org/~barbie/WWW-Scraper-ISBN-Pearson_Driver-0.08/
Search driver for Pearson Education's online catalog.
----
WWW-Scraper-ISBN-Yahoo_Driver-0.05
http://search.cpan.org/~barbie/WWW-Scraper-ISBN-Yahoo_Driver-0.05/
Search driver for Yahoo Books online catalog.
----
XML-API-0.13
http://search.cpan.org/~mlawren/XML-API-0.13/
Perl extension for creating XML documents
----
XML-MyXML-0.08
http://search.cpan.org/~karjala/XML-MyXML-0.08/
A simple XML module
----
XML-RPC-0.1
http://search.cpan.org/~daan/XML-RPC-0.1/
Pure Perl implementation for an XML-RPC client and server.
----
grepmail-5.3033
http://search.cpan.org/~dcoppit/grepmail-5.3033/
search mailboxes for mail matching a regular expression
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: 1 Mar 2007 23:37:09 -0800
From: krakle@visto.com
Subject: Re: Perl and MySQL
Message-Id: <1172821029.487503.90230@64g2000cwx.googlegroups.com>
On Feb 28, 11:44 am, "Charles A. Landemaine" <landema...@gmail.com>
wrote:
> I have a MySQL table that is used to store comments on my blog. I just
> found out it's filled with spam.
> The table itself is 2 GB big, with
> more than half a million spam backlinks.
Unless a bot flooded your script with a half million comments in a day
you should of known about this "abuse" way before you reach 10,000
spam messages. Web Master 101 - monitoring your web site.
> I haven't found much material
> on how to interact between Perl and MySQL. What I'd like to do is do a
> simple Perl script that opens the DB table, goes through all rows and
> deletes all those which contain "<a href". I'll have to do that during
> the night, not to disrupt the server. How could I do that?
How could you do that! Why would you do that?! Perl is basically
useless and irrelevant when it comes to the solution of your problem.
Look at what you have to do...
Loop through the table row by row deleting all rows that contain "<a
href".
No where in that operation does it require the use of Perl. It's all
(and only) mySQL relevant.
Since you have to check row by row, indexes aren't important. So, at 3
am run this query:
DELETE FROM myTable WHERE myColumn = '%<a href%';
This is a mySQL solution to a mySQL problem.
------------------------------
Date: 02 Mar 2007 08:10:38 GMT
From: tadmc@augustmail.com
Subject: Posting Guidelines for comp.lang.perl.misc ($Revision: 1.7 $)
Message-Id: <45e7dbf6$0$3158$ae4e5890@news.nationwide.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.7 $)
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.augustmail.com/~tadmc/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 <tadmc@augustmail.com> and many others on the
comp.lang.perl.misc newsgroup.
------------------------------
Date: Thu, 1 Mar 2007 23:29:29 -0600
From: Len Philpot <len@philpot.org>
Subject: Re: Q on regex of LWP::Simple data
Message-Id: <epdxww5gfd0l.5psw3jcl6it4$.dlg@40tude.net>
On Fri, 02 Mar 2007 16:02:12 +1100, Iain Chalmers wrote:
> In article <18p2wnf2hexfv$.gfqj1nv2jaiq.dlg@40tude.net>,
> Len Philpot <len@philpot.org> wrote:
>
>> my @cachepage = \
>> get('http://www.geocaching.com/seek/cache_details.aspx?wp=GC115K4');
>>
>
> I don't think @cachepage contains what you think it contains...
>
> try adding:
>
> use Data::Dumper;
> print Dumper \@cachepage;
>
> after that line.
So, it's one long string now... $#cachepage == 1
What's the best way to break it back up again? Maybe a pointer in the
right direction?
The get() example used a scalar instead of an array, but I wanted to
iterate through it to find a number of specific strings. Maybe I need to
come up with a regex to simply extract what I need all at once without
iterating.
Or am I looking at this wrong? My final objective, more or less, is to
retrieve a file from a website and extract two or three specific strings
from it, located via a couple of specific HTML tags and subsequently
extracted using back references, but I'm not there yet.
Perhaps I'm being dense... After all, it /has/ been a very long
DST-fix-infested day :-)
Thanks.
--
---- Len Philpot -------- l e n @ p h i l p o t . o r g (no spaces)
------- ><> ------------- http://pages.suddenlink.net/lenphilpot/
------------------------------
Date: Fri, 02 Mar 2007 17:39:51 +1100
From: Iain Chalmers <bigiain@mightymedia.com.au>
Subject: Re: Q on regex of LWP::Simple data
Message-Id: <bigiain-7A50F6.17395102032007@news.usenetmonster.com>
In article <epdxww5gfd0l.5psw3jcl6it4$.dlg@40tude.net>,
Len Philpot <len@philpot.org> wrote:
> On Fri, 02 Mar 2007 16:02:12 +1100, Iain Chalmers wrote:
>
> > In article <18p2wnf2hexfv$.gfqj1nv2jaiq.dlg@40tude.net>,
> > Len Philpot <len@philpot.org> wrote:
> >
> >> my @cachepage = \
> >> get('http://www.geocaching.com/seek/cache_details.aspx?wp=GC115K4');
> >>
> >
> > I don't think @cachepage contains what you think it contains...
> >
> > try adding:
> >
> > use Data::Dumper;
> > print Dumper \@cachepage;
> >
> > after that line.
>
> So, it's one long string now... $#cachepage == 1
>
> What's the best way to break it back up again? Maybe a pointer in the
> right direction?
>
> The get() example used a scalar instead of an array, but I wanted to
> iterate through it to find a number of specific strings. Maybe I need to
> come up with a regex to simply extract what I need all at once without
> iterating.
>
> Or am I looking at this wrong?
Yep. LWP::Simple::get doesn't return an array of lines no matter _how_
much you want it too.
Either split the scalar you get into an array of lines yourself
@cachepage=split(/\n/,$scalar_version_ofOcachepage);
or throw the whole scalar at an appropriate regex.
>My final objective, more or less, is to
>retrieve a file from a website and extract two or three specific strings
>from it, located via a couple of specific HTML tags and subsequently
>extracted using back references, but I'm not there yet.
Unless the file you're getting is very well defined, the usual advice is
to parse html using an html parser. Regexs are not the right tool to
deal with arbitrary html (though your case might be far enough from
"arbitrary html" that regexs will work for you).
big
--
"Everything you love, everything meaningful with depth and history,
all passionate authentic experiences will be appropriated, mishandled,
watered down, cheapened, repackaged, marketed and sold to the people
you hate." Mr Jalopy quoting Hooptyrides (on jalopyjunktown.com)
------------------------------
Date: 2 Mar 2007 02:01:53 -0800
From: "Kari" <kari.k.saarela@gmail.com>
Subject: SOAP::Lite serializer or version problem
Message-Id: <1172829713.024396.101270@n33g2000cwc.googlegroups.com>
Hi,
I'm just starting with Perl and SOAP::Lite package so please be
patient. The problem that I'm facing is that I have a quite simple
webservice that I want to call. I managed to do so reading thry
examples and docs. Then I updated my SOAP:Lite package to most recent
version (0.69 I guess) from CPAN. Now the same script won't work with
the webservice. With a little debuggin' I found that the SOAP call to
the webservice is totally different now. And I think I need set
something to serializer to get "old format" back. If somebody please
would give some pointers and maybe and example it would be greatly
appreciated.
I'll paste here the input data +trace option gave me.
So I this is the working call that gave me results:
<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope xmlns:xsi="http://www.w3.org/1999/XMLSchema-
instance" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsd="http://www.w3.org/1999/XMLSchema" SOAP-
ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
<SOAP-ENV:Body>
<namesp1:execute xmlns:namesp1="urn:XXX">
<CustDataByIdInput_1>
<password xsi:type="xsd:string">xxxxxx</password>
<systemId xsi:type="xsd:string">xyx</systemId>
<username xsi:type="xsd:string">DRM</username>
<customerId xsi:type="xsd:int">98747</customerId>
<maxAmount xsi:type="xsd:int">1</maxAmount>
<queryId xsi:type="xsd:string"/>
</CustDataByIdInput_1>
</namesp1:execute>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
After update the same script produces this kind of call:
<?xml version="1.0" encoding="UTF-8"?>
<soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
soap:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body>
<execute xmlns="urn:XXX">
<CustDataByIdInput_1>
<password xsi:type="xsd:string">xxxxxx</password>
<systemId xsi:type="xsd:string">xyx</systemId>
<username xsi:type="xsd:string">DRM</username>
<customerId xsi:type="xsd:int">98747</customerId>
<maxAmount xsi:type="xsd:int">1</maxAmount>
<queryIdxsi:type="xsd:string" />
</CustDataByIdInput_1>
</execute>
</soap:Body>
</soap:Envelope>
and finally here's part of the script
my $service = SOAP::Lite
-> uri('urn:XXX')
#-> encoding('iso-8859-1')
-> proxy('http://xxx.xxx.xxx.xxx:xxxx/custdatabyid-jaxrpc/cust-
data-by-id')
my $result= $service -> execute (SOAP::Data-
>name("CustDataByIdInput_1" =>
\SOAP::Data->value(
SOAP::Data->name("password" => 'xxxxxx'),
SOAP::Data->name("systemId" => 'xyx'),
SOAP::Data->name("username" => 'DRM'),
SOAP::Data->name("customerId" => $cust),
SOAP::Data->name("maxAmount" =>'1'),
SOAP::Data->name("queryId" => ''))));
brgds,
Kari
------------------------------
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 186
**************************************
