Hi Jeff,
Perfect, thanks a lot, I pretty much agree with your view. > SPDY and WebSockets I may underestimate the importance of these protocols. I believe I haven't every heard about a real-world application using these protocols. I would be interested to hear the opposite. Anyway, these are probably add-ons with little impact on the stability of existing functionality, so that should be "mostly harmless". > shiny new feature I'd consider Web servers as "infrastructure" to Web apps, in the same way as operating systems and hardware are infrastructure. Innovation has moved away from the infra- structure and towards other areas (business models, mobile, ...). I'd agree with you that IPV6 and drivers for new backends are just these measures to alliviate migration pressure. The most shiny features that I see in AOLserver/NaviServer are in the area of scalability and reliability. However, the scalability discussion in the media is completely dominated by "big data", non-SQL and similar stuff. So I guess we've got a PR problem here. Maybe Gustaf should write an article about his large-scale installations. > survey Maybe some of the OpenACS guys here in the list could setup a "simple-survey" on www.openacs.org. We could also set this up on www.project-open.org if you like. What are the fields? - Name, email and company (textfields, optional) - Number of installations (number) - Average size of users per installation (number) - Hardware platform (textfield) - Operating System (textfield) - AOLserver version (textfield) - OpenACS version (textfield) - Custom software (textarea) - What I most like about AOLserver (textarea) - What I most dislike about AOLserver (textarea) - Most wanted new features/improvements (textarea) > ]po[ We've thought a bit about what we (]po[) expect from a new version of AOLserver. The truth is: not much (for the core of ]po[). Just please continue with Win32 and fix the memory bloat issue in 4.5.1 (or recommend an appropriate TCL version or whatever). One last comment: Is it really necessary to have separate AOLserver and NaviServer versions? The community is already small and now there are (partly?) redundant efforts. Cheers! Frank -----Original Message----- From: Jeff Rogers [mailto:dv...@diphi.com] Sent: Tuesday, October 02, 2012 9:46 PM To: Frank Bergmann Cc: aolserver-talk@lists.sourceforge.net Subject: Re: [AOLSERVER] Roadmap, Live Cycle & Windows Support Frank Bergmann wrote: > Hi! > > > I believe that it is important to consider the current phase of the > "live cycle" of AOLserver in order to focus the roadmap on the > important stuff: > > - AOLserver is "mature" software, there were relatively > few changes in the last few years. There are very > large productive installations relying on AOLserver. I agree with this; we should be very careful to maintain compatibility and continue support of existing functionality. It seems there's a consensus that it's worthwhile to maintain windows support. > - AOLserver is close to the end of it's live cycle, > because there are few new installations. Instead, > many users and projects have already migrated away > towards Apache etc. > > - New features will probably convince few additional > people to use AOLserver. These I'm not so sure of. New features may or may not attract new people, but my larger concern is that without certain new features (e.g., support for new protocols like SPDY and WebSockets, and interfaces to popular infrastructure bits like memcache or NoSql databases) there will be increasing pressure to migrate away. > - Instead, and that would be my conclusion, new versions > of AOLserver should reduce the migration pressure for > existing users and allow the existing user to extend > the lifetime of their installations. This I agree with; but as above, a shiny new feature in apache/node.js/ngnix/etc that aolserver doesn't match creates migration pressure. > Would you agree with this assessment? Maybe we should have a survey > who is still using AOLserver really... I'd be very interested in seeing such a survey also. OpenACS and ]po[ are definitely the most visible users, but I think they are far from the only ones. -J ------------------------------------------------------------------------------ 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
