[AOLSERVER] AOLServer documentation
Hi all, Where is the AOLserver online doc these days? I was using http://dev.aolserver.com/wiki/Tcl_API but that is erroring now. Mike Gahan Architect / Analyst / Developer / Fixer AOL (EU) Limited Tel: +44 (0) 20 7348 8857 Email: mike.ga...@corp.aol.com AIM: mikegahanuk 68 Hammersmith Road London W14 8YW www.aol.co.uk www.aol.co.uk/mediaspace Try our new products http://beta.aol.co.uk/ This e-mail, its content and any files transmitted with it are confidential and may be legally privileged. If you receive it in error or are not the intended recipient you must not copy, distribute or take any action in reliance upon it. Instead, please notify us immediately by telephoning +44 (20) 7348 8000 - ask for the Legal Department - and delete the material from your systems. In the UK, AOL Europe is a business carried on by AOL (UK) Limited, a company registered with the Registrar of Companies for England and Wales under number 3462696. Registered office: 68 Hammersmith Road, London, W14 8YW. -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to lists...@listserv.aol.com with the body of SIGNOFF AOLSERVER in the email message. You can leave the Subject: field of your email blank.
Re: [AOLSERVER] AOLServer documentation
I have copies of some docs here: http://rmadilo.com/files/as23docs/index.html http://rmadilo.com/files/docs/toc.html http://rmadilo.com/files/nsapi/ And various other info under: http://rmadilo.com/files/ and Tcl, AOLserver and related docs: http://junom.com/document/ You can search the almost the entire AOLserver source code at: http://junom.com/gitweb/gitweb.perl?p=aolserver.git (using pickaxe) Also the changelogs might help in the last one. tom jackson On Wed, 2009-06-03 at 11:16 +0200, Gahan, Mike wrote: Hi all, Where is the AOLserver online doc these days? I was using http://dev.aolserver.com/wiki/Tcl_API but that is erroring now. Mike Gahan Architect / Analyst / Developer / Fixer AOL (EU) Limited Tel: +44 (0) 20 7348 8857 Email: mike.ga...@corp.aol.com AIM: mikegahanuk 68 Hammersmith Road London W14 8YW www.aol.co.uk www.aol.co.uk/mediaspace Try our new products http://beta.aol.co.uk/ This e-mail, its content and any files transmitted with it are confidential and may be legally privileged. If you receive it in error or are not the intended recipient you must not copy, distribute or take any action in reliance upon it. Instead, please notify us immediately by telephoning +44 (20) 7348 8000 - ask for the Legal Department - and delete the material from your systems. In the UK, AOL Europe is a business carried on by AOL (UK) Limited, a company registered with the Registrar of Companies for England and Wales under number 3462696. Registered office: 68 Hammersmith Road, London, W14 8YW. -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to lists...@listserv.aol.com with the body of SIGNOFF AOLSERVER in the email message. You can leave the Subject: field of your email blank. -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to lists...@listserv.aol.com with the body of SIGNOFF AOLSERVER in the email message. You can leave the Subject: field of your email blank.
Re: [AOLSERVER] AOLServer documentation
Hi Mike, The same stuff (I think) that was on dev.aolserver.com is on http://panoptic.com/wiki/aolserver/AOLserver_Wiki I am not sure which was most up-to-date. Dossy, do you look after the dev.aolserver.com site? I think it can not connect to the database any more. Nick 2009/6/3 Gahan, Mike mike.ga...@corp.aol.com: Hi all, Where is the AOLserver online doc these days? I was using http://dev.aolserver.com/wiki/Tcl_API but that is erroring now. Mike Gahan Architect / Analyst / Developer / Fixer AOL (EU) Limited Tel: +44 (0) 20 7348 8857 Email: mike.ga...@corp.aol.com AIM: mikegahanuk 68 Hammersmith Road London W14 8YW www.aol.co.uk www.aol.co.uk/mediaspace Try our new products http://beta.aol.co.uk/ This e-mail, its content and any files transmitted with it are confidential and may be legally privileged. If you receive it in error or are not the intended recipient you must not copy, distribute or take any action in reliance upon it. Instead, please notify us immediately by telephoning +44 (20) 7348 8000 - ask for the Legal Department - and delete the material from your systems. In the UK, AOL Europe is a business carried on by AOL (UK) Limited, a company registered with the Registrar of Companies for England and Wales under number 3462696. Registered office: 68 Hammersmith Road, London, W14 8YW. -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to lists...@listserv.aol.com with the body of SIGNOFF AOLSERVER in the email message. You can leave the Subject: field of your email blank. -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to lists...@listserv.aol.com with the body of SIGNOFF AOLSERVER in the email message. You can leave the Subject: field of your email blank.
[AOLSERVER] AOLserver Documentation
Shaz will be sending out another message shortly with the list of the API's we need people to sign up to document. We're going to use SorceForge's tasks manager to keep track of these. I went ahead and added the nsv commands. Thanks to David Siktberg for signing up for these! Here's an interesting snippet from a post to comp.lang.tcl. "BTW: I've been extremely pleased with the quality of the Tcl manpages. Tcl is the only scripting language for which I have been able to write extentions using only the manpages as a reference. Perl/Python... needed to by a book and even then the documentation was very thin." We'll know we've succeeded when we get the same sort of praise for the AOLserver docs. Have a great weekend! - n
Re: [AOLSERVER] aolserver documentation
Dossy wrote: I also don't feel that the documentation sucks. I think sorely out of date may be more accurate, Sometimes I hate continuing a discussion that seems very off track. What is better, an exhaustive O'Reilly 'Definitive Guide', or relatively complete docs and a community willing to help someone who has at least read the docs that exist? I can count on one hand the new commands introduced over the last three years. The commands that are poorly documented, will probably never be useful to anyone unable to read through the C source. Even a complete novice, like me when I stumbled onto AOLserver, should be able to figure out how to get things working. And things have significantly inproved over the last three years. I'm not complaining or arguing with Dossy or anyone else who contributes to this discussion, rather, I just wonder why we all rush to apologize to someone who doesn't even appear to have set up a site using AOLserver. If someone's use of AOLserver depends on other people's opinion of the completeness of the docs, what can we say? The truth is these docs are pretty much consistent with any O'Reilly 'Definitive Guide', after a chapter or two tacked onto the front of the book so bookstore junkies actually buy the book, you have a listing of the API, and no real examples. What you really need is to be able to ask a question and get an answer in a reasonable amount of time. Use the discussion groups! Another truth is that if you can program in Tcl, picking up the AOLserver api is going to be a snap. So anything that teaches you Tcl will teach you AOLserver. I would recommend Ousterhout's _Tcl and the Tk Toolkit_ , which might be slightly outdated, but offers the best overall coverage of the why and how of Tcl. --Tom Jackson
Re: [AOLSERVER] aolserver documentation
BLAARGH. My question has been answered so this god-forsaken thread I started can die. This is all degenerating into a discussion that has already happened countless times in countless software threads... I've heard enough concerns, whetherv alid or invalid, about the amount and quality of aolserver resources to ask if there were any projects to improve and expand what is here, however good it may be at this point. Thanks to all you guys that gave productive input and pointed me in the direction of other aolserver resources. -derek Sometimes I hate continuing a discussion that seems very off track. What is better, an exhaustive O'Reilly 'Definitive Guide', or relatively complete docs and a community willing to help someone who has at least read the docs that exist? I can count on one hand the new commands introduced over the last three years. The commands that are poorly documented, will probably never be useful to anyone unable to read through the C source. Even a complete novice, like me when I stumbled onto AOLserver, should be able to figure out how to get things working. And things have significantly inproved over the last three years. I'm not complaining or arguing with Dossy or anyone else who contributes to this discussion, rather, I just wonder why we all rush to apologize to someone who doesn't even appear to have set up a site using AOLserver. If someone's use of AOLserver depends on other people's opinion of the completeness of the docs, what can we say? The truth is these docs are pretty much consistent with any O'Reilly 'Definitive Guide', after a chapter or two tacked onto the front of the book so bookstore junkies actually buy the book, you have a listing of the API, and no real examples. What you really need is to be able to ask a question and get an answer in a reasonable amount of time. Use the discussion groups! Another truth is that if you can program in Tcl, picking up the AOLserver api is going to be a snap. So anything that teaches you Tcl will teach you AOLserver. I would recommend Ousterhout's _Tcl and the Tk Toolkit_ , which might be slightly outdated, but offers the best overall coverage of the why and how of Tcl. --Tom Jackson = 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/
Re: [AOLSERVER] aolserver documentation
That was me. :-) I just ran etags on the aolserver source and M-. in emacs, very cool. The worst part of looking at source was trying to find where stuff is defined -- but no more! Jerry Asher wrote: 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. Earlier someone asked what a tag file is (I apologize, I took my system down to replace some components and came back up to discover my MX provider had changed servers without notifying me) Basically tag tables are a typically a project specific description of the files and entrypoints that make up a software in the project. Generated by etags, tag tables are used by emacs as a source of project metadata. It enables the user to go directly to the source of a function, procedure, or method. It enables the user to search through all the files in a project for some specific string. It's part of the 80% solution that makes emacs into an IDE. Folks have used etags and some regular expression strings to support LISP, C, Tcl, Tcl with ACS extensions, and PL/SQL. And many other languages I am sure. Here's what emacs has to say about the subject: A tags table is a description of how a multi-file program is broken up into files. It lists the names of the component files and the names and positions of the functions (or other named subunits) in each file. Grouping the related files makes it possible to search or replace through all the files with one command. Recording the function names and positions makes possible the `M-.' command which finds the definition of a function by looking up which of the files it is in. Tags tables are stored in files called tags table files. The conventional name for a tags table file is `TAGS'. Each entry in the tags table records the name of one tag, the name of the file that the tag is defined in (implicitly), and the position in that file of the tag's definition. Just what names from the described files are recorded in the tags table depends on the programming language of the described file. They normally include all functions and subroutines, and may also include global variables, data types, and anything else convenient. Each name recorded is called a tag. Enjoy, Jerry = Jerry Asher [EMAIL PROTECTED] 1678 Shattuck Avenue Suite 161Tel: (510) 549-2980 Berkeley, CA 94709Fax: (877) 311-8688
Re: [AOLSERVER] aolserver documentation
Kris Rehberg wrote: Rather than having the entire list membership share their opinion over and over that the documentation sucks, please join us and submit corrections to the Bug Tracker, Category: Other:Documentation, Group: documentation: http://sourceforge.net/tracker/?atid=103152group_id=3152func=browse Let me go on the record as saying the AOLserver documentation does not 'suck.' I have seen documentation that sucked -- and I have used AOLserver for some time, and the documentation has never sucked. It may not be in the same tight shape now as it was in 2.1/2.2/2.3 days, but, then again, there's not the same full-time doc person on the payroll either. I have seen much worse documentation than the current 3.x set, believe you me. So, Kris, the 'entire list membership' doesn't feel that way. While everything can stand improvement (and I have seen some improvement in various areas in the last little while), the documentation could be much worse. -- Lamar Owen WGCR Internet Radio 1 Peter 4:11
Re: [AOLSERVER] aolserver documentation
On 2001.05.01, Lamar Owen [EMAIL PROTECTED] wrote: So, Kris, the 'entire list membership' doesn't feel that way. While everything can stand improvement (and I have seen some improvement in various areas in the last little while), the documentation could be much worse. I also don't feel that the documentation sucks. I think sorely out of date may be more accurate, but even then I'm not too sure -- probably 90% of what the docs cover haven't changed anytime recently. What I would like to see is the source for the documentation checked into CVS, so that we could maintain it that way. ;-) As far as I know, Scott Goodwin has brought a lot of the currently existing documentation into DocBook XML (or am I confused) -- if we could just get that checked into CVS so that anyone could update it, and have an automated build process that shoves it through some processor to spit out HTML and PDF ... we'd be all set! - Dossy -- Dossy Shiobara mail: [EMAIL PROTECTED] Panoptic Computer Network web: http://www.panoptic.com/
[AOLSERVER] aolserver documentation
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. The acs kind of accomplishes that to an extent -- except you pretty much have to use the acs, which I don't want to do. Are there any aolserver documentation projects in the works for these future releases? I garauntee it would make a difference. Anyway, just wondering... -derek = 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/
Re: [AOLSERVER] aolserver documentation
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 161Tel: (510) 549-2980 Berkeley, CA 94709Fax: (877) 311-8688
Re: [AOLSERVER] aolserver documentation
Jerry Asher 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 ---^ I'm going to expose my extreme ignorance, what is a tag file? 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 161Tel: (510) 549-2980 Berkeley, CA 94709Fax: (877) 311-8688
Re: [AOLSERVER] aolserver documentation
At 21:42 4/30/2001, you wrote: (..) the number one complaint is that the documentation sucks Absolutely! Aolserver + tcl thing is described close to unacceptable. It was a great surprise for me that variables from submited form are not available. I wasted couple of days to find a solution. Anybody with php background would be confused I guess.
Re: [AOLSERVER] aolserver documentation
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 161Tel: (510) 549-2980 Berkeley, CA 94709Fax: (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/
Re: [AOLSERVER] aolserver documentation
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). This is mildly off-topic, but sometimes my curmudgeonly nature gets the better of me. My wife worked for a while consulting on mechanical engineering with GM. General Motors, not genetically modified... The car people. For every model of car, GM *does* reinvent the wheel. And the headlight. And the fender. And everything else in the car. The same general principles apply to each design, but the design is always different. That's why the car looks and functions as a coherent unit. The moral of the story is that wheels often need reinventing, even though you need some design guidelines from previous efforts. This is what I tell people when they use the phrase reinventing the wheel. And it's not even close to germane to the current topic. So carry on. By the way, I agree. The AOLserver documentation sucks. That's because we're all geniuses who don't really need documentation. Periodically one or more of us gets a bee in a bonnet to redo or at least improve the documentation, and eventually I'm sure something will come of it. Michael
Re: [AOLSERVER] aolserver documentation
I found AOLserver after learning the basics of ASP and IIS. At the time the documentation for AOLserver was complete, yet thin, in stark compairison to ASP, which was released without much documentation at all. The AOLserver docs haven't changed at all in the last three years, not even the location. Now I constantly search for documentation on simple things like CSS or JavaScript, for the very occasional use. These technologies must be so easy to understand that no-one really documents them on the web. Probably I'm just a poor surfer. There are only two things to know to get started with AOLserver: 1-- the API is complete, so if you were wishing if it just did 'x', it probably does. 2-- the answer to your question can be found by visiting http://aolserver.com/docs/ or asking around at one of the few discussion groups. Same advice applies if you have been using AOLserver for the past 3 years. --Tom Jackson
Re: [AOLSERVER] aolserver documentation
It would certainly be nice to have at least one O'Reilly text devoted to AOLserver. When asked, I believe O'Reilly didn't see the market for it, and that's hard to deny.
Re: [AOLSERVER] aolserver documentation
TIGHT. This is what I like to see. Very awesome. -derek --- Dossy [EMAIL PROTECTED] wrote: On 2001.04.30, ricard helene [EMAIL PROTECTED] wrote: It would just be cool to have a better resource for aolserver knowledge -- preferably compiled by those who know it best. I volunteer my wiki, the AOLserver Wiki at http://panoptic.com/wiki/aolserver as the home for this resource. I've created a new page, the AOLserver Cookbook at http://panoptic.com/wiki/aolserver/AOLserverCookbook whose format should be question-and-answer, but answers should be provided in independently usable code fragments. If nothing else to get this started, I personally will answer ALL questions asked in as timely a fashion as I can reasonably manage. - dossy -- Dossy Shiobara mail: [EMAIL PROTECTED] Panoptic Computer Network web: http://www.panoptic.com/ = 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/
