Well, I guess what I'm saying is that from the point
of view of a tech guy looking for a new web solution,
aolserver resources are not as visible as for, say,
zope or apache.
With one of the big selling points of aolserver being
that it's used by aol, I think some people expect a
larger resource library behind it. Things like
architectural and engineering tips and tricks under
different circumstances, quick scripts for building
sites and things like that.
I've had many people tell me, "I believe you that
aolserver is faster and more efficient than xxx
webserver, but with php there is a vast repository of
scripts and documents that allow me to not have to
reinvent the wheel to do a simple thing." Of course,
the end result of that logic is a sucky site, but it
is an example of most people I've gotten to start
using aolserver who say the availability of technical
documentation for aolserver is just not up to snuff in
comparison to other weaker webservers, and that can
have an effect on final decisions (unfortunately).
I brought up the acs because I frequently pillage
their vast amounts of info they've put out for things
that i mentioned above -- the problem is that alot of
the time it's acs-oriented so i have to pick and
choose.
-derek
--- Jerry Asher <[EMAIL PROTECTED]> wrote:
> 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
=====
"Are you going to spend the rest of your life selling sugar water, or are you going to
come with me and change the world?"
__________________________________________________
Do You Yahoo!?
Yahoo! Auctions - buy the things you want at great prices
http://auctions.yahoo.com/
