Basel, Freitag, 11. Januar 2002, 10:26:28
.
*see original email below*
Hello David
Bricolage is a full-featured, enterprise-class content management
system. It offers a browser-based interface for ease-of use, a
full-fledged templating system
Seeing through Dave Rolsky's Exception::Class and
Sig::PackageScoped has let me make the following module, called
Exception::Handler.
In fact I rarely use $SIG{__DIE__} for exception handling, but the
concept of the module would be a bit interesting. Especially
eval { };
if
The Sapphire Cat wrote:
Documentation for these functions reads as follows:
$r-get_basic_auth_pw
If the current request is protected by Basic authentication, this
method will return 0, otherwise -1. [snip]
ok, that's unclear (and not 100% correct, either). I'd change it to:
If the
Hi, I have written a mod_perl handler that
"require" other Perl modules; these modules use the pragma
'warnings' (i.e. 'use warnings').
When I start httpd I get this message in error log:Can't upgrade that
kind of scalar (#1) (P) The internal sv_upgrade routine
adds "members" to an SV,
On Fri, 2002-01-11 at 01:29, [EMAIL PROTECTED] wrote:
Do you provide a demo of Bricolage. Can I expect something similar to
the Midgard Project on PHP?
Unfortunately there is no demo of Bricolage at this time. But you can
start reading up on it and see some screenshots at
On 11 Jan 2002, David Wheeler wrote:
On Fri, 2002-01-11 at 01:29, [EMAIL PROTECTED] wrote:
Do you provide a demo of Bricolage. Can I expect something similar to
the Midgard Project on PHP?
Unfortunately there is no demo of Bricolage at this time. But you can
start reading up on it and
On Fri, 2002-01-11 at 11:39, Matt Sergeant wrote:
Looks neat!
Thanks, Matt!
Any chance of supporting more template systems in the future, like TT and
XSLT?
The templating architecture is managed via subclasses. So anyone who
wants to add his/her favorite templating system is welcome to
On Fri, 11 Jan 2002, Matt Sergeant wrote:
Any chance of supporting more template systems in the future, like TT and
XSLT?
Adding more Burners (brictalk for templating system) is definitely
something we're interested in. If you'd like to give it a try there's a
brief set of instructions in
At 01:48 PM 1/10/2002 -0500, Perrin Harkins wrote:
You can actually use subroutines without fear! Also, reducing the amount of
magic (i.e. all of that package generation and eval stuff that Registry
does) can help clear up confusion. And you can use __END__ and __DATA__.
Good point.
I
For file organization, I'm thinking of making all page modules start
with a common namespace substring (e.g. Projectname::Page) to distinguish
them from the support (model) modules
I like to name the top level modules SiteName::Control::* and the model
modules SiteName::Model::*. Calling the
Stathy Touloumis [EMAIL PROTECTED] wrote:
For some reason the call to 'push_handlers' does not seem to register the
'handler' with mod_perl correctly when used in the code below. It seems
that only a few initial requests will successfully be processed by this
handler. It then just seems to be
For what it is worth - I would encourage you to check out the Error package
as well.
Rather than:
eval { };
if ($@-isa('FooException')) {
# ...
} elsif ($@-isa('BarException')) {
# ...
} else {
# ...
}
You would have:
try {
code;
} catch FooException
Makes sense, will look over the docs again.
Thanks,
Stathy Touloumis [EMAIL PROTECTED] wrote:
For some reason the call to 'push_handlers' does not seem to register the
'handler' with mod_perl correctly when used in the code below. It seems
that only a few initial requests will successfully
On Fri, 11 Jan 2002, Jay Lawrence wrote:
For what it is worth - I would encourage you to check out the Error package
as well.
Rather than:
eval { };
if ($@-isa('FooException')) {
# ...
} elsif ($@-isa('BarException')) {
# ...
} else {
# ...
}
You would
Hi all -
I assume I'm not the only one seeing a rash of formmail spam lately.
I don't have it on my system, but I get a handful of attempts at
using it every day. This is the kind of thing I'm talking about:
/cgi-bin/formmail.pl?[EMAIL PROTECTED],subject=Your%20site%20is%20great![EMAIL
I assume I'm not the only one seeing a rash of formmail spam lately.
Is THAT what it is? I have a Yahoo mail account which someone has been
sending literally thousands of messages per day to, CC'ing lots of
people on every one, and they all appear to be from some kind of
compromised form
This is an interesting approach to using $SIG{__DIE__} together with
eval {} blocks, without relying on the value of $^S which sometimes goes
broken. I guess we should add this trick to the guide.
Original Message
Subject: Re: [ID 20020107.001] $^S is sticky
Date: Mon, 7 Jan
On Fri, 11 Jan 2002, Perrin Harkins wrote:
I assume I'm not the only one seeing a rash of formmail spam lately.
Is THAT what it is? I have a Yahoo mail account which someone has been
sending literally thousands of messages per day to, CC'ing lots of
people on every one, and they all
On Fri, 11 Jan 2002, Tatsuhiko Miyagawa wrote:
use Exception::Handler
MyException = \my_handler,
AnotherException = \another_handler,
__DEFAULT__ = \default_handler;
eval { MyException-throw }; # my_handler()
eval {
19 matches
Mail list logo
