[30994] in Perl-Users-Digest
Perl-Users Digest, Issue: 2239 Volume: 11
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Fri Feb 27 06:09:43 2009
Date: Fri, 27 Feb 2009 03:09:07 -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, 27 Feb 2009 Volume: 11 Number: 2239
Today's topics:
Re: Develop a PERL WEB SERVICE that utilizes the Yahoo <tim@burlyhost.com>
Re: Develop a PERL WEB SERVICE that utilizes the Yahoo <cwilbur@chromatico.net>
Re: Develop a PERL WEB SERVICE that utilizes the Yahoo <tim@burlyhost.com>
Develop a PERL WEB SERVICE that utilizes the Yahoo Web <tfgordon@buffalo.edu>
Re: Develop a PERL WEB SERVICE that utilizes the Yahoo <RedGrittyBrick@spamweary.invalid>
Re: Develop a PERL WEB SERVICE that utilizes the Yahoo <tfgordon@buffalo.edu>
Re: Develop a PERL WEB SERVICE that utilizes the Yahoo <tfgordon@buffalo.edu>
Re: Develop a PERL WEB SERVICE that utilizes the Yahoo <ben@morrow.me.uk>
new CPAN modules on Fri Feb 27 2009 (Randal Schwartz)
Posting Guidelines for comp.lang.perl.misc ($Revision: tadmc@seesig.invalid
Using Perl to connect a Linux box to Linux/Windows boxe <schaitan@gmail.com>
Re: Using Perl to connect a Linux box to Linux/Windows <ben@morrow.me.uk>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Thu, 26 Feb 2009 20:00:05 -0800
From: Tim Greer <tim@burlyhost.com>
Subject: Re: Develop a PERL WEB SERVICE that utilizes the Yahoo Web Services API
Message-Id: <9zJpl.73661$qt3.66345@newsfe10.iad>
seef gordon wrote:
>
> 1. Develop a PERL WEB SERVICE that utilizes the Yahoo Web Services
> API's so
> that you can offer a Yahoo Search via your own perl webpage. So,
> you'll have to utilize the cpan/ppm tools to install the SOAP::Lite
> perl module, then, you'll need to create a web form and a perl script
> that will utilize the web services provided by Yahoo.
What issues are you having doing this? Are you getting errors or
inconsistent results, or unexpected results? Is there a portion of
code you're having trouble with? Your posy sounded more like an
outline or statement, or job description, rather than a question and
asking for help with something specific. Please elaborate.
--
Tim Greer, CEO/Founder/CTO, BurlyHost.com, Inc.
Shared Hosting, Reseller Hosting, Dedicated & Semi-Dedicated servers
and Custom Hosting. 24/7 support, 30 day guarantee, secure servers.
Industry's most experienced staff! -- Web Hosting With Muscle!
------------------------------
Date: Fri, 27 Feb 2009 00:25:30 -0500
From: Charlton Wilbur <cwilbur@chromatico.net>
Subject: Re: Develop a PERL WEB SERVICE that utilizes the Yahoo Web Services API
Message-Id: <86tz6go3hx.fsf@mithril.chromatico.net>
>>>>> "sg" == seef gordon <tfgordon@buffalo.edu> writes:
sg> Okay I have this project to do for my perl class as extra credit
sg> but I really don't know where exactly to start so I have just
sg> been gooing parts of the task and seeing what I can come up with
sg> so am looking for some guidance as to where to start or perhaps
sg> what exactly I would need to get this taks done thanks in
sg> advance
The problem suggests starting with SOAP::Lite. That's probably a good
place to start. It also tells you to use the Yahoo Web Services APIs --
what do you know about them? Maybe it's time to do some research.
This is extra credit for you -- this means *you* have to do the work.
If you've tried something and gotten stuck, ask a specific question.
But posting vague claims that you've "just been gooing [sic] parts of
the task" and trying to get people to offer suggestions will get you
nowhere.
Charlton
--
Charlton Wilbur
cwilbur@chromatico.net
------------------------------
Date: Thu, 26 Feb 2009 22:25:30 -0800
From: Tim Greer <tim@burlyhost.com>
Subject: Re: Develop a PERL WEB SERVICE that utilizes the Yahoo Web Services API
Message-Id: <xHLpl.49559$pX4.43055@newsfe08.iad>
seef gordon wrote:
> Okay I have this project to do for my perl class as extra credit but I
> really don't know where exactly to start so I have just been gooing
> parts of the task and seeing what I can come up with so am looking for
> some guidance as to where to start or perhaps what exactly I would
> need to get this taks done thanks in advance
>
What code do you have now? Where are you stuck? What is it doing or
not doing? Is it erroring? Is it giving unexpected results?
Inconsistent results? I'm not sure what to suggest or what to research,
since you've been given that information for the project already, so
you'll probably only be able to get help when you have something.
Otherwise someone would have to spend the time to create it for you,
and that wouldn't serve its purpose for you or the instructor. Please
post when you have something, because as it stands now, there's really
nothing to answer about to offer any help. It sounds like you know
what the assignment needs, so check out the module and service the
instructor mentioned, as it should likely be using those things to be a
valid credited assignment.
--
Tim Greer, CEO/Founder/CTO, BurlyHost.com, Inc.
Shared Hosting, Reseller Hosting, Dedicated & Semi-Dedicated servers
and Custom Hosting. 24/7 support, 30 day guarantee, secure servers.
Industry's most experienced staff! -- Web Hosting With Muscle!
------------------------------
Date: Thu, 26 Feb 2009 22:19:35 -0500
From: seef gordon <tfgordon@buffalo.edu>
Subject: Develop a PERL WEB SERVICE that utilizes the Yahoo Web Services API
Message-Id: <C5CCC5F7.2BF%tfgordon@buffalo.edu>
1. Develop a PERL WEB SERVICE that utilizes the Yahoo Web Services API's so
that you can offer a Yahoo Search via your own perl webpage. So, you'll
have to utilize the cpan/ppm tools to install the SOAP::Lite perl module,
then, you'll need to create a web form and a perl script that will utilize
the web services provided by Yahoo.
------------------------------
Date: Fri, 27 Feb 2009 09:46:20 +0000
From: RedGrittyBrick <RedGrittyBrick@spamweary.invalid>
Subject: Re: Develop a PERL WEB SERVICE that utilizes the Yahoo Web Services API
Message-Id: <49a7b66f$0$2514$da0feed9@news.zen.co.uk>
seef gordon wrote:
{Top-posting corrected}
Please don't top-post, please put replies below the part of the original
to which they refer and trim extranous material
>
> On 2/26/09 10:19 PM, in article C5CCC5F7.2BF%tfgordon@buffalo.edu, "seef
> gordon" <tfgordon@buffalo.edu> wrote:
>
>> 1. Develop a PERL WEB SERVICE that utilizes the Yahoo Web Services API's so
>> that you can offer a Yahoo Search via your own perl webpage. So, you'll
>> have to utilize the cpan/ppm tools to install the SOAP::Lite perl module,
>> then, you'll need to create a web form and a perl script that will utilize
>> the web services provided by Yahoo.
>>
> Sorry I did not say this before I am doing this project and need a little
> assistance with what exactly to do thanks in advance for any help
>
1. utilize the cpan/ppm tools to install the SOAP::Lite perl module.
2. create a web form.
3. create a perl script.
Which part are you having problems with?
--
RGB
------------------------------
Date: Thu, 26 Feb 2009 22:24:03 -0500
From: seef gordon <tfgordon@buffalo.edu>
Subject: Re: Develop a PERL WEB SERVICE that utilizes the Yahoo Web Services API
Message-Id: <C5CCC703.2DE%tfgordon@buffalo.edu>
Sorry I did not say this before I am doing this project and need a little
assistance with what exactly to do thanks in advance for any help
On 2/26/09 10:19 PM, in article C5CCC5F7.2BF%tfgordon@buffalo.edu, "seef
gordon" <tfgordon@buffalo.edu> wrote:
>
> 1. Develop a PERL WEB SERVICE that utilizes the Yahoo Web Services API's so
> that you can offer a Yahoo Search via your own perl webpage. So, you'll
> have to utilize the cpan/ppm tools to install the SOAP::Lite perl module,
> then, you'll need to create a web form and a perl script that will utilize
> the web services provided by Yahoo.
>
------------------------------
Date: Thu, 26 Feb 2009 23:41:05 -0500
From: seef gordon <tfgordon@buffalo.edu>
Subject: Re: Develop a PERL WEB SERVICE that utilizes the Yahoo Web Services API
Message-Id: <C5CCD911.31F%tfgordon@buffalo.edu>
Okay I have this project to do for my perl class as extra credit but I
really don't know where exactly to start so I have just been gooing parts of
the task and seeing what I can come up with so am looking for some guidance
as to where to start or perhaps what exactly I would need to get this taks
done thanks in advance
On 2/26/09 11:00 PM, in article 9zJpl.73661$qt3.66345@newsfe10.iad, "Tim
Greer" <tim@burlyhost.com> wrote:
> seef gordon wrote:
>
>>
>> 1. Develop a PERL WEB SERVICE that utilizes the Yahoo Web Services
>> API's so
>> that you can offer a Yahoo Search via your own perl webpage. So,
>> you'll have to utilize the cpan/ppm tools to install the SOAP::Lite
>> perl module, then, you'll need to create a web form and a perl script
>> that will utilize the web services provided by Yahoo.
>
> What issues are you having doing this? Are you getting errors or
> inconsistent results, or unexpected results? Is there a portion of
> code you're having trouble with? Your posy sounded more like an
> outline or statement, or job description, rather than a question and
> asking for help with something specific. Please elaborate.
------------------------------
Date: Fri, 27 Feb 2009 08:59:49 +0000
From: Ben Morrow <ben@morrow.me.uk>
Subject: Re: Develop a PERL WEB SERVICE that utilizes the Yahoo Web Services API
Message-Id: <5lmk76-un1.ln1@osiris.mauzo.dyndns.org>
Quoth seef gordon <tfgordon@buffalo.edu>:
> Okay I have this project to do for my perl class as extra credit
Do your own homework. You're unlikely to receive much useful help here
given that you've told us you're cheating.
Ben
------------------------------
Date: Fri, 27 Feb 2009 05:42:24 GMT
From: merlyn@stonehenge.com (Randal Schwartz)
Subject: new CPAN modules on Fri Feb 27 2009
Message-Id: <KFpMIo.uLI@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.
App-CLI-0.08
http://search.cpan.org/~alexmv/App-CLI-0.08/
Dispatcher module for command line interface programs
----
App-Framework-0.01
http://search.cpan.org/~sdprice/App-Framework-0.01/
A framework for creating applications
----
B-Hooks-OP-Annotation-0.43
http://search.cpan.org/~chocolate/B-Hooks-OP-Annotation-0.43/
annotate and delegate hooked OPs
----
Business-TNTPost-NL-0.1
http://search.cpan.org/~blom/Business-TNTPost-NL-0.1/
Calculate Dutch (TNT Post) shipping costs
----
CMS-JoomlaToDrupal-0.04
http://search.cpan.org/~hesco/CMS-JoomlaToDrupal-0.04/
migrate legacy Joomla content to Drupal
----
CPAN-Mini-Indexed-0.03_01.2
http://search.cpan.org/~nkh/CPAN-Mini-Indexed-0.03_01.2/
Index the content of your CPAN mini repository
----
CPS-0.02
http://search.cpan.org/~pevans/CPS-0.02/
flow control structures in Continuation-Passing Style
----
CatalystX-REPL-0.01
http://search.cpan.org/~flora/CatalystX-REPL-0.01/
read-eval-print-loop for debugging your Catalyst application
----
DBIx-Class-0.08099_07
http://search.cpan.org/~ribasushi/DBIx-Class-0.08099_07/
Extensible and flexible object <-> relational mapper.
----
Dackup-0.34
http://search.cpan.org/~lbrocard/Dackup-0.34/
Flexible file backup
----
Data-PostfixDeref-0.04
http://search.cpan.org/~bmorrow/Data-PostfixDeref-0.04/
Allow ->[] ->{} as an alternative to @{ } %{ }
----
DateTime-Format-Natural-0.75_02
http://search.cpan.org/~schubiger/DateTime-Format-Natural-0.75_02/
Create machine readable date/time with natural parsing logic
----
Device-OUI-1.02
http://search.cpan.org/~jasonk/Device-OUI-1.02/
Resolve an Organizationally Unique Identifier
----
Finance-Wesabe-0.01
http://search.cpan.org/~bricas/Finance-Wesabe-0.01/
Access your wesabe.com account information
----
HTTP-Session-0.30
http://search.cpan.org/~tokuhirom/HTTP-Session-0.30/
simple session
----
IO-Async-0.19
http://search.cpan.org/~pevans/IO-Async-0.19/
a collection of modules that implement asynchronous filehandle IO
----
MooseX-MethodAttributes-0.04
http://search.cpan.org/~flora/MooseX-MethodAttributes-0.04/
code attribute introspection
----
MooseX-Types-DateTimeX-0.05
http://search.cpan.org/~ecarroll/MooseX-Types-DateTimeX-0.05/
Extensions to MooseX::Types::DateTime
----
MouseX-Object-Pluggable-0.022
http://search.cpan.org/~kitano/MouseX-Object-Pluggable-0.022/
Mouse port of MooseX::Object::Pluggable
----
Muldis-D-0.60.0
http://search.cpan.org/~duncand/Muldis-D-0.60.0/
Formal spec of Muldis D relational DBMS lang
----
MySQL-Insert-0.05
http://search.cpan.org/~despair/MySQL-Insert-0.05/
extended inserts for MySQL via DBI
----
Net-LibIDN-0.12
http://search.cpan.org/~thor/Net-LibIDN-0.12/
Perl bindings for GNU Libidn
----
Net-Trac-0.10
http://search.cpan.org/~jesse/Net-Trac-0.10/
Interact with a remote Trac instance
----
Net-Twitter-2.10
http://search.cpan.org/~cthom/Net-Twitter-2.10/
Perl interface to twitter.com
----
Number-Phone-1.7
http://search.cpan.org/~dcantrell/Number-Phone-1.7/
base class for Number::Phone::* modules
----
POE-Component-Server-SimpleHTTP-1.56
http://search.cpan.org/~bingos/POE-Component-Server-SimpleHTTP-1.56/
Perl extension to serve HTTP requests in POE.
----
Regexp-Wildcards-1.03
http://search.cpan.org/~vpit/Regexp-Wildcards-1.03/
Converts wildcard expressions to Perl regular expressions.
----
Rose-DB-0.750
http://search.cpan.org/~jsiracusa/Rose-DB-0.750/
A DBI wrapper and abstraction layer.
----
Rose-DB-Object-0.779
http://search.cpan.org/~jsiracusa/Rose-DB-Object-0.779/
Extensible, high performance object-relational mapper (ORM).
----
Rose-DBx-Object-Indexed-0.005
http://search.cpan.org/~karman/Rose-DBx-Object-Indexed-0.005/
full-text search for RDBO classes
----
Rose-HTMLx-Form-DBIC-0.08
http://search.cpan.org/~zby/Rose-HTMLx-Form-DBIC-0.08/
Filling Forms with data from DBIC and saving data from Forms to DBIC records.
----
SWISH-Prog-0.26
http://search.cpan.org/~karman/SWISH-Prog-0.26/
information retrieval application framework
----
Search-Sitemap-2.06
http://search.cpan.org/~jasonk/Search-Sitemap-2.06/
Perl extension for managing Search Engine Sitemaps
----
Simo-0.0806
http://search.cpan.org/~kimoto/Simo-0.0806/
Very simple framework for Object Oriented Perl.
----
Simo-Error-0.0206
http://search.cpan.org/~kimoto/Simo-Error-0.0206/
Error object for Simo
----
Simo-Wrapper-0.0208
http://search.cpan.org/~kimoto/Simo-Wrapper-0.0208/
Object wrapper to manipulate attrs and methods.
----
Storable-Ref-1.0
http://search.cpan.org/~vany/Storable-Ref-1.0/
Persistent automatic variables vi Storable
----
String-CaseProfile-0.15
http://search.cpan.org/~enell/String-CaseProfile-0.15/
Get/Set the letter case profile of a string
----
Template-Plugin-Handy-0.003
http://search.cpan.org/~karman/Template-Plugin-Handy-0.003/
handy vmethods for Template Toolkit
----
Test-Classy-0.05
http://search.cpan.org/~ishigaki/Test-Classy-0.05/
write your unit tests in other modules than *.t
----
Test-Classy-0.06
http://search.cpan.org/~ishigaki/Test-Classy-0.06/
write your unit tests in other modules than *.t
----
Test-LeakTrace-0.05
http://search.cpan.org/~gfuji/Test-LeakTrace-0.05/
Traces memory leaks
----
Test-LoadAllModules-0.02
http://search.cpan.org/~kitano/Test-LoadAllModules-0.02/
do use_ok for modules in search path
----
Test-Synopsis-0.03
http://search.cpan.org/~miyagawa/Test-Synopsis-0.03/
Test your SYNOPSIS code
----
Test-UseAllModules-0.10
http://search.cpan.org/~ishigaki/Test-UseAllModules-0.10/
do use_ok() for all the MANIFESTed modules
----
Test-Weaken-2.001_000
http://search.cpan.org/~jkegl/Test-Weaken-2.001_000/
Test that freed memory objects were, indeed, freed
----
warnings-unused-0.03
http://search.cpan.org/~gfuji/warnings-unused-0.03/
Produces warnings when unused variables are detected
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/>
Smalltalk/Perl/Unix consulting, Technical writing, Comedy, etc. etc.
See http://methodsandmessages.vox.com/ for Smalltalk and Seaside discussion
------------------------------
Date: Fri, 27 Feb 2009 08:17:29 GMT
From: tadmc@seesig.invalid
Subject: Posting Guidelines for comp.lang.perl.misc ($Revision: 1.9 $)
Message-Id: <tkNpl.17903$yr3.13366@nlpi068.nbdc.sbc.com>
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.9 $)
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_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: Fri, 27 Feb 2009 00:00:07 -0800 (PST)
From: Krishna Chaitanya <schaitan@gmail.com>
Subject: Using Perl to connect a Linux box to Linux/Windows boxes
Message-Id: <cb01301e-436d-4573-a70a-6d6d7a18a50b@v35g2000pro.googlegroups.com>
Hi all,
Is there any way in Perl to connect from a Linux box to other Linux/
Windows boxes to do 2 things - (a) copying files to these boxes and
(b) execute commands on those boxes and monitor the progress ? It is
good if this can be done with "plain vanilla" boxes......i.e. boxes
with factory-made OSes without too many extra programs installed on
them...
These are the 2 basic operations underlying a "push" installation of
software.....i've been trying to solve this problem but I don't know
the entire gamut of options available for use.......any open-source or
Perl modules available to do this for the most part? What protocols/
programs can be used?
Thanks for your time & help.
------------------------------
Date: Fri, 27 Feb 2009 09:20:53 +0000
From: Ben Morrow <ben@morrow.me.uk>
Subject: Re: Using Perl to connect a Linux box to Linux/Windows boxes
Message-Id: <lsnk76-du1.ln1@osiris.mauzo.dyndns.org>
Quoth Krishna Chaitanya <schaitan@gmail.com>:
>
> Is there any way in Perl to connect from a Linux box to other Linux/
> Windows boxes to do 2 things - (a) copying files to these boxes and
> (b) execute commands on those boxes and monitor the progress ? It is
> good if this can be done with "plain vanilla" boxes......i.e. boxes
> with factory-made OSes without too many extra programs installed on
> them...
Linux->Linux (or other unix) is easy. Pretty much all Unixes nowadays
come with sshd installed, so use one of the ssh modules on CPAN. You may
wish to configure public key access, and you will certainly need to
carefully consider the security of what you are doing. If you are
installing software you will probably need to do it as root; however,
you probably don't want to allow ssh access as root. This will mean
using sudo or some equivalent.
Linux->Windows is somewhat harder. While there are ssh servers for
Win32, I believe they all require some sort of Unix emulation
environment (Cygwin or Interix) and due to the lack of ptys under Win32
I've always found them less than satisfactory, at least for interactive
use. You may find them sufficient for your purposes, however you will
still have to install and configure the sshd server.
Ben
------------------------------
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 2239
***************************************
