Who would AOLserver appeal to the most? My first guess would be Tcl programmers, but it might be easier to introduce the API via libnsd. libnsd offers at least a few things: Data structures: ns_set nsv arrays ns_config (not sure if you can use this with just libnsd) Mutex/Concurrent programming Scheduled Procedures Database Access (Any comments on if/when/how you can load modules into a tclsh?)
How to appeal to new users? Examples, examples, examples. I don't read a dictionary to learn a language. One thing which should be easy for active programmers to contribute is code examples: how do you use commands or solve problems. I haven't contributed much in the way of documentation, but I have made available many examples of how I use the API. One possible way of organizing this would be to create a example server. There are usually three types of code: library code, registered filters and procedures and script pages: both tcl and adp. A directory structure in pageroot could be used to organize and play around with various API (tcl, nsd, modules, application code). You might be able to use the same group of pages to auto test the API. Probably my most efficient method of developing a API is to write the proc on a tcl script page and just reload the page between edits. Once done, the procedure is moved into a library file. Instead of this, I could just leave the page as an example of how to call/use the procedure. I don't think anyone is going to have any luck selling AOLserver to someone who could use Apache to do everything they want as efficiently as they need. But what would be needed to sell AOLserver to those who could benefit? My opinion is that we need examples of multi-server applications. Although there are many small customers who would like to use existing software, larger customers are more likely to realize that being able to handle growth (due to success) is more important. It would be helpful if AOL could release (I know they are getting close) nsdci and some kind of white paper to explain how they can be used. Knowing that this information is publicly available could be a good selling point. tom jackson -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
