To be honest and blunt, the community process in terms of AOLserver is rather broken, and has been for some time. The 4.5 work was done in-house here at AOL, and with limited community involvement. A lot of the "experimental" features were added to deal with specific scaling challenges we knew we would be facing here.
When decided to go ahead and release 4.5, the thought was that we would eventually finish up any backwards compatibility work that needed to be done. We also assumed that if there were issues, people would simply hold off on upgrading, or work around the issues. Would documentation have helped - of course. Would a roadmap be useful - definitely. Agree with everything you, and others are saying, but we're not there yet. Sorry. - n On 8/1/07, Rick Cobb <[EMAIL PROTECTED]> wrote: > > I mostly sympathize with your sentiments. Incompatible changes should be > documented. And design documents & directions for AOLServer belong in > public on the AOLServer wiki, not hidden. > > I.e., if when someone decided this was a good idea, there was an > "experimental features" page for 4.5 that outlined the idea, that would > at least form the basis for (a) docs, and (b) community discussion. If > someone (like you or me) needed that backward compatibility, we could > contribute it. At present, it still seems like the docs we see on the > wiki are either generated from long-ago internal documentation, or not > written at all. > > And as for roadmaps: > "Your search - roadmap - did not match any documents." > > However, I would like to point out that one of the real problems with > the AOLServer community for a while was its perceived inability to pick > up innovations. Discouraging change from inside AOL is only going to > make the problem worse. We should be encouraging experimentation -- but > with community feedback. > > -- ReC > > > -----Original Message----- > From: AOLserver Discussion [mailto:[EMAIL PROTECTED] On Behalf > Of [EMAIL PROTECTED] > Sent: Wednesday, August 01, 2007 8:57 AM > To: AOLSERVER@LISTSERV.AOL.COM > Subject: Re: [AOLSERVER] configured minthreads, maxthreads doesnt show > up with [ns_server threads] command > > > Technically everything in the configuration file is a Tcl command > > (ns_section, ns_param, etc.) so it's really not that much of a > stretch. > > But > > I agree, it is different. > > Technically, the configuration file is a bucket of bits, but that's not > a > very useful observation. > > > Had we ever actually gotten around to deploying AOLserver 4.5 > internally > > here at AOL, I'm sure we would have at least done the work to provide > some > > backwards compatibility wrappers for things like this, but as yet we > > haven't. > > Geezus. In this case, the code simply shouldn't've gone in. > > Or it should've been offered to the community in its incomplete form, > with > the offer to incorporate it in 4.5 if volunteers in the community > completed it. > > > -- > 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. > > > -- > 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. > -- Nathan Folkman [EMAIL PROTECTED] -- 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.
