cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Niclas Hedhman <>
Subject Re: [TIPS] Basic configurations of Apache 2.0 for Cocoon 2
Date Fri, 07 Feb 2003 02:01:48 GMT
On Thursday 06 February 2003 20:27, Pier Fumagalli wrote:
> On 6/2/03 3:47 am, "Niclas Hedhman" <> wrote:
> > Shouldn't you in this case have front-end load balancing routers (various
> > topologies available) to lower the load on each server?
> Wish I could... I can't have (because of a fucked up design and
> implementation before I came on board) 2 instances running (they clash on
> the database side... Who is the idiot storing the status of a cache in the
> servlet container in the database where the data to be cached is? Jules!)

Hmmm. Maybe we should re-introduce the death-penalty for programmers....

> It's not thousands of dollars, boy I'm _not_ that expensive... :-)

No?? $500 a day?

> Anyhow, the "who cares? Go and buy something off-the-shelf" attitude is
> _so_ wrong... Ok, I'll go shopping in Tottenham Ct. Road and forget about
> thinking that there might be a better and more intelligent way out???
> Gee, with that attitude noone would have even thought about writing Apache
> 2, you have such a perfect solution going and buying M$IIS off the shelf
> :-)

Well, the idea of buying a solution to "load balancing" is to free up time to 
invent in areas where no solution at all exists.
No matter how much you optimize a piece of software, you will always have a 
peak limit. Question would then be, how much time to spend for how much 
improvement, and until we reach which limit?

Let me also say, that there is an enormous difference between I spending 2 
weeks to save $3000 of purchases (which I probably won't do, "why bother"), 
compare to me spending 2 weeks to save a whole community $100 each in 
purchases (which is a lot easier to do, "grateful people").

Anyway Pier, I am happy that you (and Stefano even more so) is expressing 
"concerns" (mildly) about Tomcat and its direction. I never really liked it 
(mostly stemmed from its early problems with configurations) and stuck with 
Apache+JServ (mostly out of laziness "It ain't broke").

Are we looking into a mod_cocoon somewhere down the line?? (That would be fun)


To unsubscribe, e-mail:
For additional commands, email:

View raw message