Re: Easy Template class?

Joe Stump wrote: > > > All in all templates are freeing our resources, the designers and the > > developers can concentrate on their work instead of finding out what the > > other guys have been doing to the code. It furthers code reuse. > > Meanwhile you spend thousands more dollars on machines to handle excess load - > that or you guys aren't doing enough hits to worry about. Let me explain how > things work on a site that gets millions of hits a DAY - you put ONE slightly > unoptimized query one the site and BAMB the site comes down (we have 6 dual > fullons with 1GB of RAM a piece for nodes and a Sun 420R for a DB with a > netapp 760 for storage), you add ONE extra layer of fat and your nodes are > going to go bonkers. It's just the way it is. The way we work it at our place > is we have a concept phase, the designers create that, and then we make it come > to life. We don't have that big sites, no. I do agree that more layers are bad, but we have to do a trade off. In projects I know of, done by a much larger company than ours for a governmental branch here in Norway, they use MSSQL server in one end, then a database generalization engine, then an XML layer, then an XSSLT layer, then an application layer (or whichever row they place all this in). When I look into that many headed monster I feel that the excesses we indulge in actually benefits the client and user and that the trade off is minimal. Though I think our shop would be better off doing comparisons to someone doing work in the Unix world as opposed to the Windows hell:) Might I inquire into which sites you are responsible for? As a side note, it is hard getting qualified people, it is easy to get more hardware. Some choices are easy to make based on the circumstances. We will have to reevaluate our stance the day we are as lucky as to make it big time with what we do. Now we're serving our clients and they are very satisfied with our work and efforts. -- Paul K Egell-Johnsen Developer/PR Manager eZ systems as http://ez.no/