At 11:42 AM 4/30/01 -0700, you wrote:
>I've read a couple of messages about newer versions of
>aolserver to be released and I have a question.
>
>At my last company, we were using a drastically
>inferior system for our web solution and we needed
>something better. I happened upon aolserver and was,
>myself, pretty thoroughly convinced of its worthiness.
>
>However, I've shown it to many people since then --
>most who agree that it would be a great solution...
>the number one complaint is that the documentation
>sucks (in comparison to projects like apache or zope.)
> I know for a fact that more people would jump on
>aolserver if it had more extensive docs and more code
>examples and things like that.
I know Scott Goodwin is working on aolserver documentation.
I have found AOLserver documentation really very nice in actual use. I
printed out the Admin manual, and the AOLserver Tcl dev manual and read
through them. AOLserver is really pretty small in some ways and it's by
no means onerous to print out and read the manuals. Having read them and
having them available is nice, but most days I use google to find AOLserver
or tcl documentation.
The documentation for most aolserver commands show up as the number choice
on google:
http://www.google.com/search?q=ns_conn
AOLserver itself is a very clean piece of code. I know it sucks to say,
read the code, but in this case, the code, emacs, a tag file, and the
various communities can get you pretty far.
Now ACS documentation? That's a different issue. (Is that what you're
asking about?)
Jerry
=====================================================
Jerry Asher [EMAIL PROTECTED]
1678 Shattuck Avenue Suite 161 Tel: (510) 549-2980
Berkeley, CA 94709 Fax: (877) 311-8688
