Hi Mark,
Mark Stosberg wrote:
On 2004-02-12, Steve Hay [EMAIL PROTECTED] wrote:
As the person that submitted the import() routine patch in the first
place, I feel obliged to help out.
The attached patch against 3.21 will fix your test case, and hopefully
most other problems like
Hi Jesse / Mark,
Jesse Erlbaum wrote:
Hi Mark --
I have questions about a couple of items on your CGI::App TO DO list.
One was better support for mod_perl by supporting Apache::Request. I'm
just starting to use mod_perl, so could you give me an idea of what's
involved here?
The
Mark Stosberg wrote:
Hello,
Here's a link to a updated CGI::App distribution that I'm proposing
become CGI::App 3.2:
http://mark.stosberg.com/perl/CGI-Application-3.2_mls2.tar.gz
Looks good to me -- builds and tests OK (with Cees' patch applied) using
Perl 5.8.2 on WinXP/MSVC6.
Thanks for
Mark Stosberg wrote:
The only other thing that I'd still really like is for something to be
done about the problems with exception handling that the catch/rethrow
(eval/die) in run() causes. This has been discussed at length before in
several threads (see the archives), but nothing has ever
Mark Stosberg wrote:
Hello,
Here's a link to a updated CGI::App distribution that I'm proposing
become CGI::App 3.2:
http://mark.stosberg.com/perl/CGI-Application-3.2_mls2.tar.gz
Here's a tiny but important documentation patch that corrects a mistake
in the cgiapp_postrun() description.
Darin McBride wrote:
On September 16, 2003 11:20 am, Steve Hay wrote:
Couldn't you at least revert it to its old behaviour, seeing as you're
not doing anything special with it?, e.g.
my $body = eval { $autoload_mode ? $self-$rmeth($rm) :
$self-$rmeth() };
die Error executing run
Hi,
I've just run into a serious flaw with CGI::Application which completely
breaks my exception handling.
I'm setting up a mod_perl system using C::A, and have a handler() that
looks like this:
sub handler : method {
my($class, $r) = @_;
local $SIG{__DIE__} = \catcher;
Hi,
I'm trying to figure out a good way to download dynamically generated
files (mainly PDF files and ZIP files) using CGI-Application.
The user directs his browser at a CGI script, rather than a static PDF
file or ZIP file, and that script generates the file in question based
on various
Hi John,
John Crowley wrote:
Steve,
I believe the best way would be to redirect the user to a page which has its
headers set to the appropriate MIME type. In a simple (non-C::A) CGI, you can
use the following line...
Hmm. So I use CGI-Application to generate the file and then send a
redirect
Adam Gent wrote:
Hi,
There is no reason why it can not be all done within the C::A.
If the run mode generates the file and saves it to disk as a temporary file.
The run mode can then output the correct header.
What would the correct header there be?
Do you mean redirect the client to the
Eric Andreychek wrote:
On Wed, 10 Sep 2003, Steve Comrie wrote:
You should be able to use the argument of 'none' to the CGIApp header_type()
method.
---
my $filename= 'the_pdf_file.pdf;
my $output = get_pdf_contents();
my $header= Content-Type: application/octetstream\n;
Steve Comrie wrote:
Setting $self-header_type('none'); followed by printing the headers
yourself and then opening a file in the run-mode and printing it line by
line and finally followed by return ''; *should* hypothetically solve the
problem without relying on undocumented CGIApp features.
Hi all,
Scott Hepler wrote:
FWIW, I had to change the use CGI::Carp to use Carp near the top of
CGI::Application to get useful debugging info when running from the command
line (saw this in the archive somewhere).
I couldn't help jumping on this comment as another opportunity to make
this
Hi Jesse,
I sent a mail to this list recently requesting use CGI::Carp; be
changed to use Carp;, but I got no response.
Am I to take it that you're not keen on the idea?
If so, then how about the attached patch? It provides the *option* of
disabling the use of CGI::Carp by importing a
Hi Jesse,
Jesse Erlbaum wrote:
Hi Steve --
Do you have a new ETA for 3.1? I'd really like to start getting to
grips with the new post-run stuff.
Sorry for the delay!
In the mean time, everybody should let me know if they find any problems
with the implementation of cgiapp_postrun().
Hi Jesse,
About a month ago you said in a mail to this list that you'd try to get
3.1 out this weekend, but it didn't happen, and hasn't done since
either unless I'm missing something.
Do you have a new ETA for 3.1? I'd really like to start getting to
grips with the new post-run stuff.
16 matches
Mail list logo
