Re: [AOLSERVER] the sybase driver and sql server 7
I, for one, am very interested in this idea. The odbc implementation for connecting to SQL Server 7+ databases from a non-Win32 server is not pretty. I would love to see integrated support. I will gladly help with testing, as that is all I am smart enough to help with! Ian A. Harding Programmer/Analyst II Tacoma-Pierce County Health Department (253) 798-3549 mailto: [EMAIL PROTECTED] [EMAIL PROTECTED] 04/27/01 10:09AM All in all, it looks as though an nstdsdb module will be rather straightforward. Film at 11. Jerry Asher wrote: *ponders* I have Sybase 11.x installed here, but no SQL 7 or 2000 box to test with. Hmm. - Dossy I have SQL Server 7 here and I will be happy to give you access to it. Jerry = Jerry Asher [EMAIL PROTECTED] 1678 Shattuck Avenue Suite 161Tel: (510) 549-2980 Berkeley, CA 94709Fax: (877) 311-8688
[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/
[AOLSERVER] dumb variable question
Okay -- allow me to show my ignorance. How can I set a variable that is available to all page requests until I unset it? Let's say I have the html for my webpage stored on the file system. On the first request of the page, the generator reads the html from the filesystem and stores it in a variable then displays that html. On each subsequent request, the generator makes sure the variable exists and displays the html from the variable -- and if it doesn't, it recreates from the file system. Hopefully that made sense. What I'm trying to do is cache small chunks of a page in memory by storing the html in variables. Can you do this with straight tcl, or do you have to involve the aolserver api? or do you have to do it another way? which way is best? Thanks... -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] dumb variable question
How can I set a variable that is available to all page requests until I unset it? You have these options: - Use an nsv. http://aolserver.com/docs/nsv.adp - Use ns_share. This is deprecated. - Define a proc that returns the value. This is only useful for constants, and you must know the value at startup time. - Use the ns_cache module. http://www.arsdigita.com/acs-repository/download-verify?version_id=622 Sounds like the ns_cache module might be the most appropriate for you.
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+ACS+Java = AOLServer+TCL?
I've had similar concerns. I'm not all that excited about building simple websites with overly-complex technology for the sake of impressing investors. You use the right tool for the right job. The way I see it, regardless of what direction this software goes in, we have the source code to a very good system that is running a monstrous beast of a site like aol. We can pillage what we want of the other systems and have a non-java implimentation. -derek --- Alan Wright [EMAIL PROTECTED] wrote: Having just completed a site using using Apache/Tomcat/Interbase ( http://www.free-minder.com ) at the end of last year I came across Greenspun's book. We spent many unproductive hours evaluating whether to use this or that buzzword compliant technology. Next we had to try to configure an entire software circus to address a programming model that was solved 40 years ago by IBM with the 3270 terminal. Greenspun's evangelism of the no-nonsense AOLServer + TCL really hit me between the eyes and I was convinced that my next project would go down this route. As we pull together the threads of our next project I am slightly dismayed to learn of the disputes at the top of Arsdigita as we were planning to use the ACS system as a springboard to which we would add our subscription based application. My main concern is the porting of the ACS system to Java. To me this looks rather like a fashion statement and is something I would seek to avoid because it will surely just add another tent to the circus. Is the future direction of AOLServer likely to incorporate integrated Java (and move away from TCL)? Can we safely base our software infrastructure strategy on AOLServer + TCL (with or without ACS) or does the ARSDigita move towards java presage a similar shift in AOLServer? Alan Wright = 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+ACS+Java = AOLServer+TCL?
I sure hope not. I rather enjoy the dumb looks I get when I tell people I am using aolserver, tcl and postgresql. I hope they all continue to be vastly superior products that no-one has heard of. My resume is almost completely pop buzz program free. No PHP, no Java, no Visual *, I sure hope I keep this job forever!! Ian A. Harding Programmer/Analyst II Tacoma-Pierce County Health Department (253) 798-3549 mailto: [EMAIL PROTECTED] [EMAIL PROTECTED] 04/30/01 02:33PM Having just completed a site using using Apache/Tomcat/Interbase ( http://www.free-minder.com ) at the end of last year I came across Greenspun's book. We spent many unproductive hours evaluating whether to use this or that buzzword compliant technology. Next we had to try to configure an entire software circus to address a programming model that was solved 40 years ago by IBM with the 3270 terminal. Greenspun's evangelism of the no-nonsense AOLServer + TCL really hit me between the eyes and I was convinced that my next project would go down this route. As we pull together the threads of our next project I am slightly dismayed to learn of the disputes at the top of Arsdigita as we were planning to use the ACS system as a springboard to which we would add our subscription based application. My main concern is the porting of the ACS system to Java. To me this looks rather like a fashion statement and is something I would seek to avoid because it will surely just add another tent to the circus. Is the future direction of AOLServer likely to incorporate integrated Java (and move away from TCL)? Can we safely base our software infrastructure strategy on AOLServer + TCL (with or without ACS) or does the ARSDigita move towards java presage a similar shift in AOLServer? Alan Wright
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/
