Tony Bowden wrote:
> I'd have to disagree. Maybe Mike had something different in mind when he
> created Class::DBI, but as the current active developer on it, I'm
> definitely pushing it in the R-O direction. Like Dave, I always start by
> thinking of my database schema and then Class::DBI provide
Not sure if this has been brought up before. I compiled and installed
mod_perl/1.27 via apxs like so:
$ perl Makefile.PL EVERYTHING=1 USE_APXS=1 WITH_APXS=/usr/local/sbin/apxs
$ cd apaci
$ make
$ make install
The installation went well, I did a graceful and it wouldn't restart,
instead apache
At 13:30 18.06.2002 -0400, you wrote:
>http://www.apacheadmin.com/mod_perl.html
Great. I explicitely missed this before. Especially the context information
is useful if you have to do things via .htaccess as much as possible.
Thanx,
Joachim
--
"... ein Geschlecht erfinderischer Zwerge, die fue
Just speaking as a mod_perl user/developer, I think the format of Rich's docs is
excellent. Since these are directives that belong in httpd.conf, it makes sense
for their documentation to look like the documentation of other non-perl
directives that belong in httpd.conf. Organization-wise, Rich'
On Tue, Jun 18, 2002 at 01:30:47PM -0400, Rich Bowen wrote:
> It has long frustrated me that there was no mod_perl module
> documentation, in the style of the standard Apache module documentation.
> I don't mean to bash the docs that are there - clearly, they are of
> exceptional quality. But I wa
It's not quite the truth again. It is not a private email; it is a public
mailing list. Everyone writing here expects the replies and comments from
any other subscriber, especially from the main speaker of the thread.
Igor seems upset with the current (not still final) results of this
discussion,
Rich Bowen wrote:
> It has long frustrated me that there was no mod_perl module
> documentation, in the style of the standard Apache module documentation.
> I don't mean to bash the docs that are there - clearly, they are of
> exceptional quality. But I wanted something like the standard module
>
It has long frustrated me that there was no mod_perl module
documentation, in the style of the standard Apache module documentation.
I don't mean to bash the docs that are there - clearly, they are of
exceptional quality. But I wanted something like the standard module
docs.
So, rather than compl
Ian D. Stewart wrote:
> On 2002.06.18 09:57 Stas Bekman wrote:
>
>> [CC'ing Andreas again]
>>
>>> Stas is right. The only problem I see with MP_INST_APACHE2 is the
>>> fact that using the CPAN.pm module to download the module would fetch
>>> the newest version of the module, regardless of wheth
Gregory Matthews wrote:
> Thank you for the link.
[Gregory, please remember to keep the threads on the list and not to
take them private without being asked to and worse, not sharing the
knowledge with the rest of the community]
> This is the route I would like to go (My::Exeption). Could you
[sorry for the broken References - I've just joined the list and am
replying to a post in the archives]
On Sat, 15 Jun 2002, Perrin Harkins said:
>> An Object-Relational mapper takes objects and stores them in a relational
>> database, as transparently as possible. I think the most pure example
On 2002.06.18 09:57 Stas Bekman wrote:
> [CC'ing Andreas again]
>
>> Stas is right. The only problem I see with MP_INST_APACHE2 is the
>> fact that using the CPAN.pm module to download the module would
>> fetch the newest version of the module, regardless of whether you
>> wanted the one for m
[CC'ing Andreas again]
> Stas is right. The only problem I see with MP_INST_APACHE2 is the fact
> that using the CPAN.pm module to download the module would fetch the
> newest version of the module, regardless of whether you wanted the one
> for mod_perl 2.0 or mod_perl 1.0.
That's true :(
I
* Noam Solomon <[EMAIL PROTECTED]> [2002-06-17 17:49]:
> I sent out a plea for help last week, but probably didn't provide
> enough information for a quick solution. The problem is that I'm using
> Apache::OpenIndex (which is similar to Apache::AutoIndex) and have not
> been able to get the apache
At 13:26 18.06.2002, Stas Bekman wrote:
>Andy Wardley wrote:
>>I've been playing around with Apache 2 and mod_perl 1.99 and considering
>>the changes I'll need to make to Apache::Template to make it play nicely
>>under the new world order.
>>Given that I want to continue to support Apache::Templat
At 13:22 18.06.2002, Stas Bekman wrote:
>[when suggesting things please give people some time to respond,
>especially given the crazy traffic at this list lately. I just had a
>chance to read this thread.]
Sorry.
>I'm -1 on renaming. Here is why:
I never talked about renaming. I talked about
Andy Wardley wrote:
> I've been playing around with Apache 2 and mod_perl 1.99 and considering
> the changes I'll need to make to Apache::Template to make it play nicely
> under the new world order.
>
> Given that I want to continue to support Apache::Template for v1 users,
> should I create ano
[when suggesting things please give people some time to respond,
especially given the crazy traffic at this list lately. I just had a
chance to read this thread.]
I'm -1 on renaming. Here is why:
- Not all modules fit into suggested categories, some modules belong to
several ones.
- We defin
Hi people,
Time for a post that's a little different than your usual "New user" and
"New module" e-mails :) I'm posting here since it seems like the most
appropriate place to discuss these issues.
I adressed an issue on the mod_perl list lately concerning the Apache::
namespace organization.
On Mon, 17 Jun 2002, Slava Bizyayev wrote:
> Yes, absolutely. And no one on the earth may restrict your rights to log
> anything you feel important in your own handler. Just every overhead
> decrements the number of your prospective users. And when you try to dictate
> your very own needs (or fan
At 11:31 18.06.2002, Andy Wardley wrote:
>I've been playing around with Apache 2 and mod_perl 1.99 and considering
>the changes I'll need to make to Apache::Template to make it play nicely
>under the new world order.
>
>Given that I want to continue to support Apache::Template for v1 users,
>shoul
I've been playing around with Apache 2 and mod_perl 1.99 and considering
the changes I'll need to make to Apache::Template to make it play nicely
under the new world order.
Given that I want to continue to support Apache::Template for v1 users,
should I create another module, say Apache2::Templa
22 matches
Mail list logo
