Hi,
I need some quick references and points, if anyone is free.
We've got this Mason only guy who is trying to challange our decision to
rebuild a site in Template, as opposed to Mason. My initial reasons were
that template allows us to build a more generic system which is not just
web-centred. Also that it's more usable for designers. We've got to
defend this soon. I'd appreciate some pointers about session management
approaches vs Mason custom. Also about companies using Template and other
good reasons to go with template.
Anyone up at this time?
Cheers,
Fiq
"__ __ _ __ __
| \/ | ___ __| | ___ _ __ _ __ | \/ | __ _ _ __
| |\/| |/ _ \ / _` |/ _ \ '__| '_ \| |\/| |/ _` | '_ \
| | | | (_) | (_| | __/ | | | | | | | | (_| | | | |
|_| |_|\___/ \__,_|\___|_| |_| |_|_| |_|\__,_|_| |_|
a pathetic example of his organic heritage"
- Bad Religion
