> Yes -- I think I recall Naviserver splitting because we weren't responsive at > Aol. Made sense at the time -- there was just no justification for Aol to > support the project at the time. > > Merging back makes sense. I'm guessing it's easier to fix whatever is > perceived as not working with Naviserver and freeze Aolserver than the other > way around? Just a guess. I always liked the Naviserver name better > anyway...
I'd vote for trying to get onboard the naviserver wagon, as a) they seem to have had a lot of innovation b) their documentation has apparently come a long way c) their handling of scalability, leaking and memory bloat is apparently further along than aolserver d) their project name doesn't make people cringe. Question: what does aolserver have that might need to be merged into naviserver? -john ------------------------------------------------------------------------------ Don't let slow site performance ruin your business. Deploy New Relic APM Deploy New Relic app performance management and know exactly what is happening inside your Ruby, Python, PHP, Java, and .NET app Try New Relic at no cost today and get our sweet Data Nerd shirt too! http://p.sf.net/sfu/newrelic-dev2dev _______________________________________________ aolserver-talk mailing list aolserver-talk@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/aolserver-talk
