|
Posted by Nikolas Hagelstein on 10/12/05 16:47
Hi Peter
> Controller: PHP takes URI requests. Validates form input. Produces the
>outgoing XML and passes it to the View layer once at the very end.
Is your controller approach capable of managing things like "actions
chains" etc?
Could you provide brief information on the excakt logic flow of your
approach?
Something like a diagram would be nice ;)
>With all the SQL dialects this really possible when queries get complicated?
I agree ....100% abstraction would affect flexibility...so the way is
to find a
compromise between abstraction/flexibility...same to the form thing.
>Templating I've tried Smarty
Me too ...but i don't like it for serveral reasons..
Just to clarify things i do not indend to point out "THE ULTIMATIVE"
frameworkt/templateparser - whatever combination.
But if it exists i would be glad to hear about it ;)
The goal is to give an overview what combinations are passable and what
are their
main/optimal purposals.
e.g.:
use mojavi + smarty...because...
if you got much DB stuff i did good experience on
STUDS + PEAR:DB because....but beware because it lacks of ....
If we could carry together a few scenarios that would be a great
guideline
for those who are looking for an entry to a more professional way of
php development.
Regards,
Nikolas
Navigation:
[Reply to this message]
|