Perrin Harkins wrote:
There are tutorials on the Template Toolkit site, a recent perl.com
article about TT and Class::DBI, and my article:
http://perl.apache.org/docs/tutorials/apps/scale_etoys/etoys.html
I read Perrin's case study awhile ago and it was excellent. Out of
curiosity (and since most
Hi Eric,
class. What I'd like is to have my model (as in MVC) objects reuse the
process or maybe even server shared objects without doing any of these:
1. Using a singleton utility class
2. Needing to pass objects to model objects' new() in teh controllers
3. Instantiating the objects in
On Thu, 24 Jul 2003 02:18:17 -0400
Eric Sammer [EMAIL PROTECTED] wrote:
Perrin - Have you ever considered revealing more about the Etoys
project or just the concepts as you applied them? It would be nice to
peek at some of the details. Or, is this an NDA situation or some such
thing? Either
Frank Wiles wrote:
I too would like to would like to have a better understanding of how
MVC can be applied to mod_perl. Maybe even HelloWorld sized example
showing how all of the different components interact?
No examples, but Andy Wardley sent a great email to the Template
Toolkit
## NOTE : Very simple example which for the most part
## will seem like overkill and it is. Typically the complexity
## of the application can be reduced by breaking it into the
## components below. It makes for easier maintenance.
## Model responsible for data retrieval not formatting.
##In
On Thu, 2003-07-24 at 09:20, Frank Wiles wrote:
I too would like to would like to have a better understanding of how
MVC can be applied to mod_perl. Maybe even HelloWorld sized example
showing how all of the different components interact?
There's one of those in my original article.
Aaron Ross wrote:
Hi Eric,
class. What I'd like is to have my model (as in MVC) objects reuse the
process or maybe even server shared objects without doing any of these:
1. Using a singleton utility class
2. Needing to pass objects to model objects' new() in teh controllers
3. Instantiating the
On Thu, 2003-07-24 at 02:18, Eric Sammer wrote:
where did you (Perrin) keep
objects like your database handle (assuming DBI, but please correct
otherwise) and any objects that could be reused (TT, XML parser objects,
et al)?
People seem to ask about this frequently, but I don't think we
Perrin Harkins wrote:
On Thu, 2003-07-24 at 02:18, Eric Sammer wrote:
where did you (Perrin) keep
objects like your database handle (assuming DBI, but please correct
otherwise) and any objects that could be reused (TT, XML parser objects,
et al)?
People seem to ask about this frequently, but I
On Thu, 2003-07-24 at 15:17, Eric Sammer wrote:
Maybe a stupid question, but what would be the functional difference
between dumping the object after each request like you say and using the
same method as you describe for the TT object below? I ask because I'm
currently treating both
Title: Re: Application design patterns
Perrin Harkins wrote:
The biggest thing the article didn't cover is the ideas
used by the guys coding the more interactive parts of the
application to express the state machine implemented by
each of their modules in a declarative data structure
On Thu, 2003-07-24 at 17:22, Garrett Goebel wrote:
Perrin Harkins wrote:
The biggest thing the article didn't cover is the ideas
used by the guys coding the more interactive parts of the
application to express the state machine implemented by
each of their modules in a declarative data
Hi, All
Are there some common application design patterns using mod_perl + TT2
? Any links would be greatly appreciated
Sincerely
Alex
On Wed, 2003-07-23 at 18:18, Aleksandr Guidrevitch wrote:
Are there some common application design patterns using mod_perl + TT2
? Any links would be greatly appreciated
There are tutorials on the Template Toolkit site, a recent perl.com
article about TT and Class::DBI, and my article:
http
14 matches
Mail list logo
