> > TurboGears has some problem which I don't think can be overcome: > > > > 1. Unfamiliar templating language. The UI for the "user" section of > > this site will be coded by someone other than me. That someone is > > already familiar with the Smarty PHP templating system. And would be > > reluctant to switch to Genshi or Cheetah. > > This isn't a problem with TG, it's a problem with your UI coder.
** You are correct. My OP was incorrectly worded. I should have said: "I would have problems using TG, some of which I don't think can be overcome." I like TG very much. I have used it for the last year, and have contributed to its code-base. > > 2. Need to restart the server. [...] It also requires that template > > designers, potentially unaware of their actions, have access to a site- > > restart mechanism. > > Only if you do direct changes on a live system. Even though agile is > in, I don't think you really want to be /that/ agile on a production > system. > > > b. If controller code is changed, and has significant bugs for some > > reason, this causes the server process to die, or refuse to start. > > This can cause even more down-time. > > See above. Now you are doing untested code changes on a live > production system??? ** I would say that I am "doing" mildly-tested code on a live production system, because that's the way my employer wants it. In my industry, quality and correctness of code comes second to rolling out more websites with shinier functionality. I sympathise with your position on this issue, but it is not the position of my employer. This discussion has somewhat renewed my drive, however, to change my employer's mind. Does anyone have suggestions as to testing and rolling-out practices for TG sites? Furthermore, is anyone running a TG site across multiple machines, serving requests in parallel? If so, I would love to open up a dialog with you. I'm particularly curious about practices for synchronised restarting of servers after code upgrades, and for avoiding the down-time that involves. My first (and only, to date) high-traffic TG site was coded to run across multiple machines. It uses no local caching, and uses memcached for everything. This required the use of Cheetah, however. Which is not ideal, since one cannot yet code widget templates in Cheetah. This requires the use of two template languages, which my employer certainly won't like. Thanks very much, Stuart --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/turbogears?hl=en -~----------~----~----~----~------~----~------~--~---
