modperl_pro_design_patterns

This is part of The Pile, a partial archive of some open source mailing lists and newsgroups.



Subject: Re: RFC: mod_perl advocacy project resurrection (and a proposal!)
From: kyle dawkins <kyle@centralparksoftware.com>
Date: Thu, 7 Dec 2000 13:56:46 -0500

On Thu, 07 Dec 2000 11:33, you wrote:
> On 7 Dec 2000, David Hodgkinson wrote:
> > Development are two of the bibles. I have to say though,
> > I've avoided the Design Patterns type books purely
> > because of the C++/Java bias.
>
> you sure are missing out.


I second that.  You should lose your anti-engineering bias just because of 
your anti-Java/C++ bias.  Design patterns have nothing whatsoever to do with 
Java and C++, and if you ignore them, you ignore solutions to problems that 
plague every developer.  Design patterns are fundamental to everything we do, 
even if we don't know it.  That's not to say that they will somehow solve all 
your problems, but a responsible developer should learn about as many 
problem-solving techniques as possible.

Ok, I'll get off my soapbox now.

:-)

===

Subject: Re: RFC: mod_perl advocacy project resurrection (and a
From: Gunther Birznieks <gunther@extropia.com>
Date: Fri, 08 Dec 2000 09:07:55 +0800

I would agree. If you want to see design patterns in practical action with 
relation to mod_perl.. go to

http://www.extropia.com/ExtropiaObjects/

and skim through Chapters 10 (App Architecture) and on (on the individual 
app toolkit components). Each one contains a sidebar on how design patterns 
affected the design of our application toolkit for CGI and mod_perl.

===


the rest of The Pile (a partial mailing list archive)

doom@kzsu.stanford.edu