On Mon, 30 Apr 2001, Perrin Harkins wrote:
> I've tried that, but last time I went with more general
> classes of exceptions containing unique error IDs
> (defined in a constants module) to indicate the exact
> type. Not as Java-like, but it did save me from
> creating dozens of classes with no
on 4/30/01 8:47 PM, brian moseley at [EMAIL PROTECTED] wrote:
> On Mon, 30 Apr 2001, Jeffrey W. Baker wrote:
>
>> type of exception. Right now I cannot in fact think of
>> any program I have written that branches on the type of
>> exception. Java encourages this with multiple catch
>
> in CP
Eeyore here, again, less happy than ever. S.O.S.
okay. i try to use the Ticket*.pm modules from the book
(chapter 6) verbatim and they work well for well-behaved
browsers.
to widen the workability (i.e. to make it functional for
badly-mannered browsers*) i'm trying some workarounds.
this is a P
On Mon, Apr 30, 2001 at 05:47:03PM -0700, brian moseley wrote:
> On Mon, 30 Apr 2001, Jeffrey W. Baker wrote:
>
> > type of exception. Right now I cannot in fact think of
> > any program I have written that branches on the type of
> > exception. Java encourages this with multiple catch
>
> in
On Mon, 30 Apr 2001, Jeffrey W. Baker wrote:
> type of exception. Right now I cannot in fact think of
> any program I have written that branches on the type of
> exception. Java encourages this with multiple catch
in CP Web Mail, the underlying libraries throw typed
exceptions so that the appl
On Mon, Apr 30, 2001 at 07:54:24PM -0400, Robert Landrum wrote:
> >On Mon, Apr 30, 2001 at 03:46:03PM -0400, Geoffrey Young wrote:
> >> > From: will trillich [mailto:[EMAIL PROTECTED]]
> >> > Sent: Monday, April 30, 2001 3:31 PM
> >> > To: [EMAIL PROTECTED]
> >> > Subject: forbidden vs. cookie
> >
At 03:24 PM 4/30/01 -0700, Jeffrey W. Baker wrote:
>On Mon, 30 Apr 2001, Matt Sergeant wrote:
>
> > On Mon, 30 Apr 2001, Jeffrey W. Baker wrote:
> >
> > > Yes precisely. It used to be that you could only die() with a
> string, but
> > > 5. gave us die() with a reference to an object and at tha
>On Mon, Apr 30, 2001 at 03:46:03PM -0400, Geoffrey Young wrote:
>> > From: will trillich [mailto:[EMAIL PROTECTED]]
>> > Sent: Monday, April 30, 2001 3:31 PM
>> > To: [EMAIL PROTECTED]
>> > Subject: forbidden vs. cookie
>> [snip]
>> ># this don't work so hot, neither:
>> >
On Mon, Apr 30, 2001 at 03:46:03PM -0400, Geoffrey Young wrote:
> > From: will trillich [mailto:[EMAIL PROTECTED]]
> > Sent: Monday, April 30, 2001 3:31 PM
> > To: [EMAIL PROTECTED]
> > Subject: forbidden vs. cookie
> [snip]
> > # this don't work so hot, neither:
> > $r->he
On Mon, Apr 30, 2001 at 03:46:17PM -0400, Ken Y. Clark wrote:
> Here is some code I've used in the past in a mod_perl app to
> set a cookie and do a redirect at the same time. I believe it
> works for most browsers -- or at least this code has been
> working for over a year and I haven't heard to
On Mon, 30 Apr 2001, Jeffrey W. Baker wrote:
> I have learned that errors from down in the call stack are very rarely
> conditionally recoverable. If I call obj->method(), and it throws an
> exception, there are few situations where the cause of the exception
> matters at all. In most cases I w
Title: RE: Exception modules
unsubscribe please- thanks
-Original Message-
From: Matt Sergeant [mailto:[EMAIL PROTECTED]]
Sent: Monday, April 30, 2001 4:29 PM
To: Jeffrey W. Baker
Cc: [EMAIL PROTECTED]
Subject: Re: Exception modules
On Mon, 30 Apr 2001, Jeffrey W. Baker wrote:
>
On Mon, 30 Apr 2001, Matt Sergeant wrote:
> On Mon, 30 Apr 2001, Jeffrey W. Baker wrote:
>
> > Yes precisely. It used to be that you could only die() with a string, but
> > 5. gave us die() with a reference to an object and at that moment
> > the system was complete. The creation of a rationa
Matt Sergeant <[EMAIL PROTECTED]> wrote:
> It doesn't seem any different from Error.pm to me, except in syntax.
> Maybe you could expand on why/where it is different?
OK, yes, it *is* very similar in principle - I would perhaps have been
better to have added to Graham's code, but I suffer from
On Mon, 30 Apr 2001, Jeffrey W. Baker wrote:
> Yes precisely. It used to be that you could only die() with a string, but
> 5. gave us die() with a reference to an object and at that moment
> the system was complete. The creation of a rational exception object type
> is left to the discretion of
Hmm.. i just got it to build ok on RH 7.0..
I'll see if I can just use those binaries...
oh.. i did forget to mention the 6.1 box was an SMP kernel.
Not sure if that could be an issue, but thought it could be
important
/a
alan arbizu wrote:
>
> Hi folks...
>
> I've got an issue here that all
On Mon, 30 Apr 2001, Matt Sergeant wrote:
> On Mon, 30 Apr 2001, Jeffrey W. Baker wrote:
>
> >
> >
> > On Mon, 30 Apr 2001, Matt Sergeant wrote:
> >
> > >
> > > > [1] for my Perl exception package (yes, another one :) which, in its
> > > > development version, now mostly does the Right Thing fo
Hi folks...
I've got an issue here that all the rtfm'ing on my part has not
been able to resolve :/
Here's the setup
RH 6.1
Apache 1.3.19
mod_ssl 2.8.1
mod_perl 1.25
php 4.0.4pl1
building all from source
So...
I first configured mod_ssl by pointing it at the apache source...
Then I configur
On Mon, 30 Apr 2001, Jeffrey W. Baker wrote:
>
>
> On Mon, 30 Apr 2001, Matt Sergeant wrote:
>
> >
> > > [1] for my Perl exception package (yes, another one :) which, in its
> > > development version, now mostly does the Right Thing for mod_perl. See
> > > http://sourceforge.net/projects/perle
On Mon, 30 Apr 2001, Matt Sergeant wrote:
>
> > [1] for my Perl exception package (yes, another one :) which, in its
> > development version, now mostly does the Right Thing for mod_perl. See
> > http://sourceforge.net/projects/perlexception/ for the curious.
>
> Since I'm doing the mod_perl ex
> [1] for my Perl exception package (yes, another one :) which, in its
> development version, now mostly does the Right Thing for mod_perl. See
> http://sourceforge.net/projects/perlexception/ for the curious.
Since I'm doing the mod_perl exception handling talk at TPC, I feel
obligated to ask
I've been off this list for over a year, so I may be covering ground that
I've failed to find in the archives, but whatever...
I've had occasion to examine the internals of Apache::Registry recently[1]
and have been reminded of the unfeasably long package names that it
generates for scripts.
Hi there,
On Sat, 28 Apr 2001, MCALLISTER,RONAN (HP-FtCollins,ex1) wrote:
> HP-UX 10.20
> and compiling from source.
Did you compile your Perl?
> my httpd.conf
Where?
Have you looked in the archives for HP-UX? I believe there have been
successes in the recent past, and it may have been a bi
Here's another option which may not be exactly what you're looking for, but
it will work: Once you've performed all validation and are ready to
redirect them with the cookie, rather than attempting the redirect with http
headers, just output a simple "processing" page with the redirect url in an
On Mon, 30 Apr 2001, will trillich wrote:
> Date: Mon, 30 Apr 2001 14:31:02 -0500
> From: will trillich <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Subject: forbidden vs. cookie
>
> i could really use some dumbed-down tips on setting cookies
> during a redirect. boy, this is really getting to m
>i could really use some dumbed-down tips on setting cookies
>during a redirect. boy, this is really getting to me.
>
>using apache 1.3.9 on debian 2.2/potato
>
>in trying to implement the concept of the Apache::Ticket*.pm
>modules from the Apache Modules (eagle) book in chapter 6
>(on pages 304+)
> -Original Message-
> From: will trillich [mailto:[EMAIL PROTECTED]]
> Sent: Monday, April 30, 2001 3:31 PM
> To: [EMAIL PROTECTED]
> Subject: forbidden vs. cookie
>
[snip]
>
> # this don't work so not, neither:
> $r->header_out(-cookie=>$cookie);
>
i could really use some dumbed-down tips on setting cookies
during a redirect. boy, this is really getting to me.
using apache 1.3.9 on debian 2.2/potato
in trying to implement the concept of the Apache::Ticket*.pm
modules from the Apache Modules (eagle) book in chapter 6
(on pages 304+) i'm run
On Mon, 30 Apr 2001, Ken Williams wrote:
> [EMAIL PROTECTED] (Stas Bekman) wrote:
> >On Mon, 30 Apr 2001, Matt Sergeant wrote:
> >> On Mon, 30 Apr 2001, Stas Bekman wrote:
> >> > cool, but this section in the guide was stating the CORE::format() doesn't
> >> > work. And it's still doesn't under
> Often quite a number of developers are all
> at work, and they don't all merit the kind of trust that mod_perl
> requires.
See Phillippe Chiasson's talk @ ApacheCon. Lots of developers checking out
release controlled Apache, perl, and application. Neat stuff.
John
[EMAIL PROTECTED]
[EMAIL PROTECTED] (Stas Bekman) wrote:
>On Mon, 30 Apr 2001, Matt Sergeant wrote:
>> On Mon, 30 Apr 2001, Stas Bekman wrote:
>> > cool, but this section in the guide was stating the CORE::format() doesn't
>> > work. And it's still doesn't under mod_perl. So doesn't CORE::write().
>>
>> Right, but
On Tue, 1 May 2001, Stas Bekman wrote:
> On Mon, 30 Apr 2001, Matt Sergeant wrote:
>
> > On Mon, 30 Apr 2001, Stas Bekman wrote:
> >
> > > cool, but this section in the guide was stating the CORE::format() doesn't
> > > work. And it's still doesn't under mod_perl. So doesn't CORE::write().
> >
>
On Mon, 30 Apr 2001, Matt Sergeant wrote:
> On Mon, 30 Apr 2001, Stas Bekman wrote:
>
> > cool, but this section in the guide was stating the CORE::format() doesn't
> > work. And it's still doesn't under mod_perl. So doesn't CORE::write().
>
> Right, but it would be nice to point to an alternati
On Sun, 29 Apr 2001 13:52:05 +0800
Gunther Birznieks <[EMAIL PROTECTED]> wrote:
I completely agree with the assertion that applications sell the
underlying technology. History teaches us that to be indisputable.
Also while applications should be an overall part of the vision, it may
not have to
--
mod_perl digest
April 22, 2001 - April 28, 2001
--
Recent happenings in the mod_perl world...
Features
o
Folks, I'm looking for some feedback regarding what IPC techniques
are being used in conjunction with mod_perl. I know about IPC::Shareable,
IPC::ShareLite. What other IPC modules/techniques are you using? Or not
using because they don't work/aren't stable/whatever. I'm interested in
any experienc
Thanks! This works for me, I don't have Apache::Filter loaded, but the
effect is the same.
My new code:
my $stdin = tied *STDIN;
my $stdout = tied *STDOUT;
untie *STDIN;
untie *STDOUT;
my $child = open3 ($cgi_in, $cgi_out, $cgi_error, $filename);
tie *STDIN, ref $stdin, $stdin;
tie *STDOUT, ref
Scott Alexander ([EMAIL PROTECTED]) said something to this effect on
04/27/2001:
> Should this work in a startup.pl file
>
> my $hostname = $ENV{"HOSTNAME"} ;
>
> from the prompt I can write echo $HOSTNAME and get the correct
> hostname of the server.
>
> But from within startup.pl I don't g
On Mon, 30 Apr 2001, Stas Bekman wrote:
> cool, but this section in the guide was stating the CORE::format() doesn't
> work. And it's still doesn't under mod_perl. So doesn't CORE::write().
Right, but it would be nice to point to an alternative. The module is
called Text::Reform, by the way.
-
unsubscribe [EMAIL PROTECTED]
--
Samuel Lellouche - Omatis
Expert Systèmes, réseaux et securité
E-mail: [EMAIL PROTECTED]
Tel: 01 53 14 59 14 / 01 53 14 59 31
40 matches
Mail list logo
