Matthew Weigel wrote:
This is the same model, albeit with better performance characteristics
(assuming kernel threads), that Apache uses, and one of the great things about this model is that it's very easy to tightly control what memory threads share
I'm sure you're extremely bright and can do it. In an absolutely perfect world where nobody has been up late the night before and the boss hasn't moved the deadline up three weeks, I'd say that our disagreements did not matter. The real world has to do with deadlines and working with people who are (1) tired (2) unfamiliar with the code in question (3) unfamiliar with the problem (4) pulled from another project (5) under great pressure to do something RIGHT NOW (6) impatient (7) want to show off how smart they are by making something very very complicated (8) trying to move the code from version 1.23A of the spec to 2.01B which has subtle differences or (9) all of the above I've made a great deal of money over my working life disproving that "easy" statement by replacing code which was intended to do as you say with what I consider to be properly isolated separate processes. The code has been shorter and performance has not suffered. And bugs have been simple to find and fix, and relatively not many. geoff steckel
