Re: HTTP Class

Manuel, we obviously have different approaches to things, but could you please tone down your attacks a bit. Calling us communists because we don't do things the way you prefer is rather strong. You say PEAR has the wrong approach because we prefer to have just one definitive class for each problem. And that your approach is better because you can have 8 different classes that do the same thing in different ways. There is obviously a need for diversity, but sometimes you need just one way to do things. Imagine if there were 10 different syntaxes for a while() loop in PHP? At a certain point you need to set a style and stick with it. PEAR is an attempt to get a unified set of classes written in a unified manner with consistent documentation and predictable naming, etc. Many people have asked for this, so that is what were are providing. This does not preclude other people from writing their own collections of classes obviously, but I fail to see why you are so dead set against the PHP team trying to pull such a collection together using the same team approach that has built PHP over the years. Yes, we have maintainers and people who manage this and thus sometimes contributions are rejected because it doesn't fit within the PEAR framework nicely for whatever reason. This also happens throughout the development of PHP. Without some control and oversight by people who have the larger picture in mind we will end up with chaos. PHP is one of the most open Open Source projects around. There are over 200 people who have CVS write access to the PHP tree. Very very few projects have been so open and I doubt you will find a project where it is easier to get an account. -Rasmus