You need to change your tone of voice John. If anyone has been have crying foul, and won't accept test results. It is you.
I have shown you a valid apache configuration that is comparable to lighttpd, for the sake of this thread it is important to show that apache can too have a low memory footprint. I also shared yet more ways to get an even lower footprint with apache. For this I am representing a hostile environment? I think not. I am providing yet another point of view. One that you do not agree with, and this is fine, however there is no reason for your comments and your blatant ignorance and disregard for anything comparative to your point of view. Don't make yourself look like a fool with outlandish, unprecedented comments. As a member of the web2py community I do not respect your out-lashing apache. You have stepped out of line. The world has changed rapidly in the past 10 years. The emergence of ROR, jQuery, .NET, virtualization, j2se 5, git, mercurial, groovy, iphone and embedded applications, social and viral networking. All of this has attributed to changing the way we think about web, and with this we need a server that can easily support the new rapidly changing environments. Apache is not history, the simple fact is that the majority of the Internet is still running apache, and until the time that apache is below 10% of market share, it won't be history. I am a fan of cherokee, lighttpd, and others. I use apache because I am putting my company in a position to easily find someone who can manage the system I have put in place if anything happened to me. Apache is much better known in the business world. Things will change, as time goes on. This is also the reason I will not change a live production system for some tweaks that would lower my memory by a negligible amount when I have access to almost unlimited resources. I applaud your work and lightweight lighttpd configuration, and if I were to ever use lighttpd I would follow your instructions on the matter. (In fact, I am adding a link to your lighttpd slice on my apache/mod_wsgi slice). It is the ability to run web2py in almost any environment that makes web2py much more appealing to business, and you have contributed to this effort. You have done a great service to the community with your examples on lighttpd. I thank you for this. -Thadeus On Sat, Feb 20, 2010 at 6:58 PM, John Heenan <johnmhee...@gmail.com> wrote: > n't we PLEASE just move on. Apache is history for both very busy > sites and for very small resource sites. Apache did a great job and > had glorious moments despite a fundamental design flaw unsuited to the > way the web has evolved and having become bloated due to its chaotic > style of development. Please let Apache die a peaceful death without > attacking or casting a slur on those who have the nerve not to pay > homage to Apache by using something else. It is simply not appropriate > and sets up an unwelcome hostile environment for those of us who > simply want to get on with using the best tools for the job and have > this recognised, not slurred. > > mod_rewrite is not a burden. > > It allows lighttpd to serve static file for web2py instead of web2py > serving them. This is a recognised benefit of using an external web > server for web2 -- You received this message because you are subscribed to the Google Groups "web2py-users" group. To post to this group, send email to web...@googlegroups.com. To unsubscribe from this group, send email to web2py+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/web2py?hl=en.
