[30652] in Perl-Users-Digest
Perl-Users Digest, Issue: 1897 Volume: 11
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Fri Oct 3 09:09:42 2008
Date: Fri, 3 Oct 2008 06:09:07 -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 Fri, 3 Oct 2008 Volume: 11 Number: 1897
Today's topics:
Re: Basic pattern matching - baffled <63f2-oyik@dea.spamcon.org>
Re: Can I use a function ref to call a function in a we <RedGrittyBrick@spamweary.invalid>
Re: Can I use a function ref to call a function in a we <ced@blv-sam-01.ca.boeing.com>
Re: Can I use a function ref to call a function in a we <cartercc@gmail.com>
pack and hex <dontmewithme@got.it>
Posting Guidelines for comp.lang.perl.misc ($Revision: tadmc@seesig.invalid
Problems flushing my buffer! (perl) <nigel@bouteyres.com>
Re: Problems flushing my buffer! (perl) <jurgenex@hotmail.com>
Re: Problems flushing my buffer! (perl) <nigel@bouteyres.com>
Re: Proxy in perl <bhasin@pacbell.net>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Fri, 03 Oct 2008 01:54:11 -0700
From: Xainin <63f2-oyik@dea.spamcon.org>
Subject: Re: Basic pattern matching - baffled
Message-Id: <hbnbe49flodne47fdo78dg1trb8of7njtl@4ax.com>
xhoster@gmail.com wrote:
>Xainin <63f2-oyik@dea.spamcon.org> wrote:
>> Help! I don't understand why this script:
>>
>> #!perl -w
>>
>> $a = 'C:\WINDOWS';
>> $b = 'C:\WINDOWS';
>>
>> if ( $a =~ /^$b$/i ) {
>> print "matched '$a' to '$b'\n";
>> }
>> else {
>> print "UNMATCHED '$a' vs. '$b'\n";
>> }
>
>\W is special in a regex.
>
>>
>> $ta = quotemeta "$a";
>
>$a is not used as a regex, it is treated as a literal string. Protecting
>characters special to regexes in something not used that way is
>counterproductive.
>
>Xho
Thanks to all - I added strict/warnings and declared with "my", but the
key per your last comment was to change "$ta" to "$a" in my last test and
it works.
--
A waist is a terrible thing to mind.
------------------------------
Date: Fri, 03 Oct 2008 10:12:07 +0100
From: RedGrittyBrick <RedGrittyBrick@spamweary.invalid>
Subject: Re: Can I use a function ref to call a function in a web script?
Message-Id: <48e5e1e7$0$15272$fa0fcedb@news.zen.co.uk>
C.DeRykus wrote:
> On Oct 2, 11:50 am, cartercc <carte...@gmail.com> wrote:
>> Can I assign a function to a scalar as a ref in a module file and call
>> the function by using the scalar in a heredoc?This is for a web app. I
>> have three components, a module, a CGI script, and a database. This is
>> a front end to a database which runs select, update, insert, and
>> delete queries and displays the results.
>>
>> I have a bunch of standard functions in the module, such as
>> print_header(), print_footer(), print_link(), connect_to_database(),
>> etc., along with some global variables.
>>
>> I have a CGI script that starts off like this:
>> use CGI;
>> use DBI;
>> use WebModule;
>> And mostly consists of a heredocs that output pure html.
>>
>> And I have a database (Postgres).
>>
>> The CGI script contains mostly forms for passing data to the
>> database. I'm using heredocs to spit out the html. I'm finding that I
>> am repeating a bunch of code, six times now, which looks like this:
>> <td><select name="postype">
>> <option>Classified</option>
>> <option>Faculty</option>
>> <option>Lecturer</option>
>> <option>PartTime</option>
>> <option>Professional</option>
>> <option>RFP</option>
>> <option>Vacant</option>
>> </select>
>> </td>
>>
>> I can create a function that prints this to the html document, but
>> that involves ending the heredoc, calling the function, and then
>> starting the heredoc, like this:
>>
>> print <<form;
>> <!-- pure html -->
>> form
>> print_select_element_in_form();
>> print <<form;
>> <!-- more pure html -->
>> form
>>
>> Here is the question: Can I assign this function to a scalar ref in my
>> module file and call the function by using the scalar in the heredoc?
>> I'm slightly frustrated as I have spent most of the morning in a
>> futile attempt to do this (and I'm sure that I'm making some stupid
>> mistake, or maybe it can't be done.)
>>
>
> Not much easier on the eyes but
> you could pare down to a single
> print with a stacked heredoc:
>
> print <<FORM, func(), <<FORM;
> foo bar
> FORM
> bat boom
> FORM
>
my $optionlist=func(); print <<FORM
foo bar
$optionlist
bat boom
FORM
Is there anything inherently wrong with this?
--
RGB
------------------------------
Date: Fri, 3 Oct 2008 05:51:24 -0700 (PDT)
From: "C.DeRykus" <ced@blv-sam-01.ca.boeing.com>
Subject: Re: Can I use a function ref to call a function in a web script?
Message-Id: <02484d3d-8049-4db9-8517-a70bb0cc2dae@a70g2000hsh.googlegroups.com>
On Oct 3, 2:12 am, RedGrittyBrick <RedGrittyBr...@spamweary.invalid>
wrote:
> C.DeRykus wrote:
>...
>
> > Not much easier on the eyes but
> > you could pare down to a single
> > print with a stacked heredoc:
>
> > print <<FORM, func(), <<FORM;
> > foo bar
> > FORM
> > bat boom
> > FORM
>
> my $optionlist=func(); print <<FORM
> foo bar
> $optionlist
> bat boom
> FORM
>
> Is there anything inherently wrong with this?
>
Yes, that's better if there are multiple interpolations of the
same variable and then you don't
need to stack heredoc's at all.
But there was some doubt:
BenM> If the repeated HTML really
BenM> is the same every time you
BenM> can simply assign it to a
BenM> variable and interpolate
BenM> that ... otherwise, the only
BenM> way to interpolate random
BenM> expressions.
If random though, a stacked heredoc
with a single print is simpler
than the OP's code IMO. The suggested HTML::Template may be best in
the long run.
--
Charles DeRykus
------------------------------
Date: Fri, 3 Oct 2008 06:01:34 -0700 (PDT)
From: cartercc <cartercc@gmail.com>
Subject: Re: Can I use a function ref to call a function in a web script?
Message-Id: <ed65cdf8-9fc5-450a-b2c0-8b358c8b0e56@59g2000hsb.googlegroups.com>
On Oct 3, 5:12=A0am, RedGrittyBrick <RedGrittyBr...@spamweary.invalid>
wrote:
> my $optionlist=3Dfunc(); print <<FORM
> foo bar
> $optionlist
> bat boom
> FORM
>
> Is there anything inherently wrong with this?
No, there isn't. I had never used a $scalar to hold multi-line text
before, but following Ben's suggestion I assigned the entire <select>
element to a variable in the module and it worked just as I had
wanted. I didn't realize that you could do this, but now I know.
I've been playing with Lisp a lot for a few months, and am noticing a
certain amount of commonality between Lisp and Perl. Writing functions
that return data is (obviously) a common Lisp idiom, and I've been
trying to do the same in Perl. I guess that this is something that one
language supports but another language does not.
On another (longish) note, we seem to have a number of paradigms for
web applications. Roughly, they seem to fall into these categories
(the names are merely suggestive):
1. Flash - creating movies that stand in for web sites.
2. Visual (Dreamweaver, FrontPage), etc) - creating web sites by using
point and click tools.
3. Hand Coding - the way we used to do it.
4. Templating (PHP, ColdFusion, JSP, etc.) - writing web pages that
incorporate snippets of code. You write the HTML and where ever you
want functionality you insert a tag that does what you want.
5. Programming (CGI inc. Perl and Python) - writing programs that
produce HTML as output. You write the code and where ever you want
HTML you write a procedure that outputs HTML.
It seems to me that web apps that are data driven rely mostly on
Templating and Programming. By inclination and philosophy, I much
prefer Programming to Templating, although Templating seems to be used
much more than Programming. Maybe it's how we view user interfaces. I
see a user interface as incidental to the data and functionality and
like to focus on getting the requirements in code before considering
the user interface. Most of my colleagues seem to focus on the
interface first and concentrate on the functionality later (not that
we could ever make a clean cut distinction between functionality and
interface.)
Comments?
CC
------------------------------
Date: Fri, 03 Oct 2008 12:16:52 +0200
From: Larry <dontmewithme@got.it>
Subject: pack and hex
Message-Id: <dontmewithme-62C426.12165203102008@news.tin.it>
Hi,
before I go into my questions here's a little excerpt from a web site:
http://www.id3.org/id3v2-00
"The ID3 tag size is encoded with four bytes where the first bit (bit 7)
is set to zero in every byte, making a total of 28 bits. The zeroed bits
are ignored, so a 257 bytes long tag is represented as $00 00 02 01."
"The reason to use 28 bits (representing up to 256MB) for size
description is that we don't want to run out of space here."
I tried to convert 00 00 02 01 from hex to decimal by using my calc and
it gave me 513 not 257
In order to get 257 I should have done 00 00 01 01, what am I doing
wrong?
is there anyway to have "pack" to get round it?
Here's a little more from the web site:
"The three character frame identifier is followed by a three byte size
descriptor, making a total header size of six bytes in every frame."
is there anyway to have "pack" to get round this? a number value into 3
bytes? $00 $00 $00 ??
thanks ever so much!
------------------------------
Date: Fri, 03 Oct 2008 07:15:22 GMT
From: tadmc@seesig.invalid
Subject: Posting Guidelines for comp.lang.perl.misc ($Revision: 1.8 $)
Message-Id: <eEjFk.1689$fD.1345@flpi145.ffdc.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.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: Fri, 3 Oct 2008 02:57:24 -0700 (PDT)
From: Nigel <nigel@bouteyres.com>
Subject: Problems flushing my buffer! (perl)
Message-Id: <32735b58-dfa2-4f68-a920-37dba8cdfdd1@p49g2000hsd.googlegroups.com>
Hi there,
I hope you can help - I'm writing a perl program and I want it report
back to the browser
on its progress. I read the perl faq and saw that by setting $| true
the buffer would be
flushed each time I printed instead of waiting until the program
terminates. But I can't
get it to work.
I'm expecting the web page to say that it's on the job, then every
second (for 10 seconds) to say Please Wait and then at the end to say
it's finished. But what happens is I wait ten seconds for a response
and the whole lot appears at once. Any advice would be VERY welcome.
Here is my VERY basic program...
#!/usr/bin/perl -w
use strict;
use CGI::Carp qw(fatalsToBrowser);
use CGI qw(:standard escape escapeHTML);
# Force the buffer to flush
$|++;
my $i;
print << "EOF";
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://
www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
<head>
<title>Test Buffer</title>
</head>
<body>
Working on it!<br />
EOF
for ($i=0;$i<10;$i++) {
print "Please wait!<br />\n";
sleep 1;
};
print << "EOF";
All Done!
</body>
</html>
EOF
exit (0);
------------------------------
Date: Fri, 03 Oct 2008 04:30:39 -0700
From: Jürgen Exner <jurgenex@hotmail.com>
Subject: Re: Problems flushing my buffer! (perl)
Message-Id: <t40ce419pskr5p6ltlig6h87ul0qnf5qgr@4ax.com>
Nigel <nigel@bouteyres.com> wrote:
>Hi there,
>
>I hope you can help - I'm writing a perl program and I want it report
>back to the browser
>on its progress. I read the perl faq and saw that by setting $| true
>the buffer would be
>flushed each time I printed instead of waiting until the program
>terminates. But I can't
>get it to work.
>
>I'm expecting the web page to say that it's on the job, then every
>second (for 10 seconds) to say Please Wait and then at the end to say
>it's finished. But what happens is I wait ten seconds for a response
>and the whole lot appears at once. Any advice would be VERY welcome.
The whole lot appears at once _WHERE_?
Run your sample program from the command line and you will notice,that
there is the desired one second pause between each "Please wait!<br
/>".
Of course your web server typically will not transmit the HTTP response
in such small chuncks but wait until it recieves EOF. And a web browser
may not display any HTML-page until it has been downloaded completely.
But neither of these has _ANYTHING_ to do with Perl but would happen
exactly the same way no matter in which programming language the CGI
program was written in.
jue
------------------------------
Date: Fri, 3 Oct 2008 06:01:24 -0700 (PDT)
From: Nigel <nigel@bouteyres.com>
Subject: Re: Problems flushing my buffer! (perl)
Message-Id: <d1c7e452-32df-4985-a211-050e280d0656@u28g2000hsc.googlegroups.com>
On Oct 3, 1:30=A0pm, J=FCrgen Exner <jurge...@hotmail.com> wrote:
> Nigel <ni...@bouteyres.com> wrote:
> >Hi there,
>
> >I hope you can help - I'm writing a perl program and I want it report
> >back to the browser
> >on its progress. I read the perl faq and saw that by setting $| true
> >the buffer would be
> >flushed each time I printed instead of waiting until the program
> >terminates. But I can't
> >get it to work.
>
> >I'm expecting the web page to say that it's on the job, then every
> >second (for 10 seconds) to say Please Wait and then at the end to say
> >it's finished. But what happens is I wait ten seconds for a response
> >and the whole lot appears at once. Any advice would be VERY welcome.
>
> The whole lot appears at once _WHERE_?
>
> Run your sample program from the command line and you will notice,that
> there is the desired one second pause between each =A0"Please wait!<br
> />".
>
> Of course your web server typically will not transmit the HTTP response
> in such small chuncks but wait until it recieves EOF. And a web browser
> may not display any HTML-page until it has been downloaded completely.
> But neither of these has _ANYTHING_ to do with Perl but would happen
> exactly the same way no matter in which programming language the CGI
> program was written in.
>
> jue
To clarify - it all appears at once in my web browser.
So it seems I must rephrase my question and perhaps address it to a
different Group as apparently the problem isn't with my Perl as
such...but I am writing this in Perl so I guess I still have a Perl
related question: Is it possible to achieve what I want i.e. to
request my perl program from my browser and have the program tell me
the progress it is making from time to time and have that appear in my
browser in real time? My impression from what I read in the faq (and
elsewhere) was that such a thing IS possible, but perhaps I've
misunderstood. In the worked examples I saw, they talked about
'Forking' - which I understand to mean that one part of the program
responds to the browser, whilst another part carries on with the
processing. I have to say I couldn't really get my head around the
examples I saw which is why I was trying to start off simple! Thanks
for the response anyway.
------------------------------
Date: Fri, 03 Oct 2008 05:43:36 -0700
From: secSwami <bhasin@pacbell.net>
Subject: Re: Proxy in perl
Message-Id: <48E61378.5050406@pacbell.net>
Ben Morrow wrote:
> Quoth secSwami <bhasin@pacbell.net>:
>> Thanks Tim and Martein for your reponses on this. Here is what I am
>> doing to setup a simple proxy on my box localy using HTTP::Proxy module.
>>
>> #!/usr/bin/perl
>> use HTTP::Proxy;
>>
>>
>> my $proxy=HTTP::Proxy->new (port => 3128);
>>
>> $proxy->start;
>>
>>
>> Just these 4 lines starts up the proxy server on my local machine
>> listening on port 3128 and then I point my browser's proxy setting to
>> "localhost" and port "3128". This all works great. No issues there.
>>
>> However, I would like to see the URL that the user just typed in the
>> broswer and then take the URL and see if another upstream server app
>> thinks its blocked or not (a central server) and if the central server
>> returns a block then spit that out to the users browser. How can I
>> intercept the user request? and see what that request was in the code above.
>
> You need to use the ->push_filter method on the proxy object before you
> call ->start. See the documentation for HTTP::Proxy.
>
> Ben
>
Thanks Ben. I will give it a shot.
------------------------------
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 1897
***************************************
