Re: Re: Best practices in a thin-controller application

Bryce,

at least, yes ;-)

Pragmatically the real problem is to be willing to stretch your brain and 
think in identity, lifecycles, associations, communication and behaviour 
instead of 
technical things like tables, datamappers, patterns, polymorphism or 
inheritance.

OOP is about to model the complex real world as best as possible,
surely you need technical workarounds and there are differences. 
But the main point is:
real life objects are created and they live, there's not such a thing 
like persistance (just some places where they are e.g. embedded) or databases
and in the end they are destroyed.

That's one of the keys to OOP and should be your ideal.
Maybe not for every application (a compiler doesn't need this) but the 
usual business ones. 
Though hard to reach :-)


My $0.02

Amen!
;-)

========== Urspr. Mitteilung ==========
Von: Bryce Lohr <brycel@xxxxxxxxxxxxxxxxxxx>
An: don-+TOG+kmQGiFBDgjK7y7TUQ@xxxxxxxxxxxxxxxx
Datum: Thu, 24 Jul 2008 17:42:33 +0200
Betreff: Re: [fw-mvc] Best practices in a thin-controller application

Ultimately, everything will come down to some existential philosophy 
argument... :)
 
 -Bryce