Hi Dossy, > I think the reason behind both issues is because the proposed > contributions weren't that great. I'm sure this statement tweaks a lot > of people, but I think it's the truth.
I'm not the expert to verify that on the C level, but the situation was: There was a solution done by aD from Rob Mayoff and at least one version that patched the aD Part into the main 3.x line. The aD version was unmaintained with the fall of the company. And if your own company relies on AOLserver you would always like to see things incorporated into the main line rather in patches you don't know how many people use them (missing a lot of collaborative testing effort) and if they would work with the next server release. I guess the encoding/charset thing was one of the main stoppers for a lot of people to join the AOLserver community. So at that time it was not easy to understand why existing _and_ working code was not incorporated. Optimizations and code refactorings are always possible later on. JMHO. > The upside is that in 4.1.x, expect to see a better way of handling the > whole encoding/charset mess, along with better support for non-HTTP > protocols in the core. Done right. (Yes, it's another major > contribution from Jim Davidson.) Thats great. The current discussion, your RoadMaps, Feature Lists etc. reveal a lot of information. It would be great to have developments like these from the Core developers being summarized early on the Wiki! > > No matter if the changes are led by a Core Team or a Steering > > Committee, the important step would be decisions at all. > > For better or worse, I think I've been good about making decisions and > following through as best I can. Of course! I like the activities that are going on! With "decisions at all" I specifically meant the result of all of what is being talked about in the moment. Everything is a process (tm). Bernd. -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
