Re: HTTP Class

Manuel, there are plenty of reasons to run PHP development and also PEAR development the way it is done. And there are also plenty of reasons to sometimes reject contributions. That doesn't mean we don't appreciate contributions. We definitely do. But without some level of control there is no way to ensure code quality. And in the end someone needs to step up and make these decisions. In PHP development that isn't just a few people. It is a lot of people each of them pretty good at what they do. There is also a very good reason to have everything in one CVS tree. It makes it easier for people to contribute to a wide variety of classes. And if some basic feature in PHP is changed we can easily go through and fix all the classes without having to chase down hundreds of individual authors. This has nothing to do with communism, elitism, or any sort of personal vendettas against anybody. There is simply a group of people who feel this way of doing things produces good code quickly. You obviously disagree. What happens if someone uploads an absolutely horrible piece of code full of security holes to your class repository? Does it go in unchanged? Does someone go through and delete bad code so unsuspecting users out there don't get burned by bad code they download from your site? In the PHP/PEAR world the code would either get rejected completely, or more likely, since the code is checked into a common repository, someone would clean it up and fix the glaring problems in it. I see nothing wrong with this approach. -Rasmus