Forum OpenACS Q&A: AOLserver advocacy
A client is wondering about AOLserver and the mass toolkit market. Hes basically asking whats this AOLserver thing? Nobody uses that. Its a valid query and we usually respond with its the web server behind aol.com is that enough for you? (obviously not phrased that glibly ). Here his concerns are also to do with the fact that designers who normally use ASP may have difficulties with ADP. Cant see why myself.
Does anyone have a stock advocacy reply they use when clients query this kind of thing?
Maybe someone can come up with something similar to dotlrn and place it in openacs.org. Or put the stuff that was posted by Talli and others. These way we are ready for things.
Although I will admit that these queries about aolserver are really valid and comes up everytime I tell someone about OpenACS. Hopefully each on of us can do our small share of advocating aolserver. In the long run, the longer aolserver is a nitch, the longer openacs will become a nitch. The feature advantage of aolserver and openacs will diminish slowly over time until its not that compeling anymore. 5 years ago... nothing compares to aolserver... 2 years ago nothing compares to ACS....
So marketing and advocacy is needed to ensure our survival. Cathy's page is already link on the home page. But that is more OpenACS advocacy than aolserver.
With a designer I'm not sure I would even need to take that long.
Also, AOL's use of AOLServer extends to many of their web properties, including mapquest.com, moviefone.com, aol.com, aol-time-warner.com, netscape.com, and digitalcity.com.
From: Ciaran De Buitlear
Just to clarify: we write web sites using ADP pages which are equivalent to ASP pages.
I would consider that the web server (Apache or AOLserver) supports the toolkit. There are modifications available for Apache which support both ASP and our toolkit. Unfortunately, AOLserver doesn't support ASP which is a proprietary development environment (owned by Microsoft - maybe that's why!). Our choice of web server was based on performance and scalability for a database backed transaction processing environment - where AOLserver wins hands down over Apache in my opinion.
As you can see from this article in Linuxworld...
...AOLserver has "Strong support for database-backed Web services."... particularly with an ..."Oracle back-end".
Further "In short, AOLserver represents a packaged solution for high-volume Web sites, whereas Apache has lots of unbundled components that may be combined in various ways. "
Or this comparison of web servers on TIVEA...
..."America Online's own web server, is the backbone of the largest and busiest production environments in the world. AOLserver is a multithreaded, Tcl-enabled web server used for large scale, dynamic web sites. "
Other organisations that use AOLserver:
AOL , Netscape.com, OpenSpec Inc. (bom.com) , Fox Cable Networks , The U.S. Department of Defense .
So you could describe this as using horses (web servers) for courses (applications). I presume most web sites don't do any heavy transaction processing. I further presume that an average web design company wouldn't build a heavy database backed transaction processing web site.
Not that related... but some posts are about aolserver.
Can someone put this good stuff in the features or some other page? We will surely make use of this in the future. If not maybe just link to this thread. Our current search is not yet as good as the old search, and its still being worked on. In the mean time maybe a page or link we can use for aolserver stuff.