[AOLSERVER] installing AOL Server on WINDOWS!
hello! I'm very new to AOLServer. At present my application is in TOMCAT. I've installed postgresql on windows successfully. Now I want to use AOLServer with it. but I'm not able to find a good documentation or article at HOW TO INSTALL AOL SERVER ON WINDOWS I mean complete steps guide can any one help me? thanx in advance regards...deepti __ Do You Yahoo!? Make international calls for as low as $.04/minute with Yahoo! Messenger http://phonecard.yahoo.com/
Re: [AOLSERVER] installing AOL Server on WINDOWS!
Tell you what, I can walk you through that if you'll walk me through the same thing with PostGreSQL. I just did AOLserver last week, from the binaries, not the C source. If you need to compile it from the source I can't help you. Listers: would you want to see this on the list, or should we keep it in private email? -- Mark Hubbard: [EMAIL PROTECTED] Microsoft Certified Professional Knowledge is Power. -Original Message- From: rana deepti [EMAIL PROTECTED] To: [EMAIL PROTECTED] [EMAIL PROTECTED] Date: Wednesday, August 22, 2001 6:44 AM Subject: installing AOL Server on WINDOWS! hello! I'm very new to AOLServer. At present my application is in TOMCAT. I've installed postgresql on windows successfully. Now I want to use AOLServer with it. but I'm not able to find a good documentation or article at HOW TO INSTALL AOL SERVER ON WINDOWS I mean complete steps guide can any one help me? thanx in advance regards...deepti __ Do You Yahoo!? Make international calls for as low as $.04/minute with Yahoo! Messenger http://phonecard.yahoo.com/
Re: [AOLSERVER] installing AOL Server on WINDOWS!
If you don't put it on the list, please cc me for both the Windows install and PostgreSQL stuff. thanks, /s. Tell you what, I can walk you through that if you'll walk me through the same thing with PostGreSQL. I just did AOLserver last week, from the binaries, not the C source. If you need to compile it from the source I can't help you. Listers: would you want to see this on the list, or should we keep it in private email? -- Mark Hubbard: [EMAIL PROTECTED] Microsoft Certified Professional Knowledge is Power. -Original Message- From: rana deepti [EMAIL PROTECTED] To: [EMAIL PROTECTED] [EMAIL PROTECTED] Date: Wednesday, August 22, 2001 6:44 AM Subject: installing AOL Server on WINDOWS! hello! I'm very new to AOLServer. At present my application is in TOMCAT. I've installed postgresql on windows successfully. Now I want to use AOLServer with it. but I'm not able to find a good documentation or article at HOW TO INSTALL AOL SERVER ON WINDOWS I mean complete steps guide can any one help me? thanx in advance regards...deepti __ Do You Yahoo!? Make international calls for as low as $.04/minute with Yahoo! Messenger http://phonecard.yahoo.com/
Re: [AOLSERVER] installing AOL Server on WINDOWS!
On 2001.08.22, Mark Hubbard [EMAIL PROTECTED] wrote: I just did AOLserver last week, from the binaries, not the C source. Which binaries? Listers: would you want to see this on the list, or should we keep it in private email? The AOLserver walk-through ought to be sent to the list. If nothing else, a summary of the explanation that could possibly be turned into or used as a HOWTO. I'd then like to post it to the wiki if that's okay. -- Dossy -- Dossy Shiobara mail: [EMAIL PROTECTED] Panoptic Computer Network web: http://www.panoptic.com/
Re: [AOLSERVER] installing AOL Server on WINDOWS!
I am interested in the procedure, considering the online documentation is not accurate. At 02:25 PM 8/22/2001 -0400, you wrote: On 2001.08.22, Mark Hubbard [EMAIL PROTECTED] wrote: I just did AOLserver last week, from the binaries, not the C source. Which binaries? Listers: would you want to see this on the list, or should we keep it in private email? The AOLserver walk-through ought to be sent to the list. If nothing else, a summary of the explanation that could possibly be turned into or used as a HOWTO. I'd then like to post it to the wiki if that's okay. -- Dossy -- Dossy Shiobara mail: [EMAIL PROTECTED] Panoptic Computer Network web: http://www.panoptic.com/ Sincerely Kerry [EMAIL PROTECTED] WWW server hosting Http://mntnweb.com Kerry Barlow p.o. box 21 kirkwood ny 13795
Re: [AOLSERVER] installing AOL Server on WINDOWS!
On 2001.08.22, Kerry Barlow [EMAIL PROTECTED] wrote: I am interested in the procedure, considering the online documentation is not accurate. Can you provide a specific example of where it's not accurate? -- Dossy -- Dossy Shiobara mail: [EMAIL PROTECTED] Panoptic Computer Network web: http://www.panoptic.com/
[AOLSERVER] Error Handling
Is there any way in AOLServer to register an exception handler? What I would like to avoid is going over all the pages in my site and adding a catch statement so that if an exception is thrown, either through the tcl interpreter or or a postgresql query or action, I could catch it with a proc or page. Thanks, Vince
Re: [AOLSERVER] installing AOL Server on WINDOWS!
Dossy: It states in the Admin documentation (http://www.aolserver.com/docs/admin/tech-ch1.htm#20993) to start the server you must type nsd -t nsd.tcl in its simplest form This may work after a user has the system up and configured, however on a new install there is no nsd.tcl file. I did find a sample-config.tcl, however when i type nsd -t sample-config.tcl from the BIN directory the AOlserver says it cannot find the config file. I am guessing I need to enter a path statment in the Windows version. 2) The Online documentation TOC(table of contents) does not work either. if you go to http://www.aolserver.com/docs/admin/admin.htm and click on the TOC icon, you will get a page saying table of contents in a text link (http://www.aolserver.com/docs/index.html) clicking on this link generates an error. [Not Found The requested URL was not found on this server.] 3) Finally there is a Aolserver binary download for Windows based systems. However there is not a downloadable documentation file for Windows. The documentation files are in .tar.gz format. These are not useable on Windows. I suppose there is a convertor program someplace, but why make things difficult for a new user. I believe I came in late on this discussion, it appears like people are attempting to fix these errors I pointed out. At 02:42 PM 8/22/2001 -0400, you wrote: On 2001.08.22, Kerry Barlow [EMAIL PROTECTED] wrote: I am interested in the procedure, considering the online documentation is not accurate. Can you provide a specific example of where it's not accurate? -- Dossy -- Dossy Shiobara mail: [EMAIL PROTECTED] Panoptic Computer Network web: http://www.panoptic.com/ Sincerely Kerry [EMAIL PROTECTED] WWW server hosting Http://mntnweb.com Kerry Barlow p.o. box 21 kirkwood ny 13795
Re: [AOLSERVER] installing AOL Server on WINDOWS!
That would be fine. I've been using quite a bit of open source stuff lately
and haven't had an opportunity to give anything back yet. There's really
not much to the procedure though.
- I went to aolserver.com, to the download section, and got this:
http://aolserver.com/archive/server/binary-builds/aolserver-3.4-win32-instal
ler.exe
- It runs just like any other installer for window$. Take the defaults and
step all the way through it.
- Then you click Start/Programs/AOLserver/AOLserver. You see the console
pop up and go through its initialization. The console should stay open - if
it disappears you have a problem that caused AOLserver to terminate. Copy
the AOLserver shortcut and paste it into a DOS command prompt - then you can
see what happened without the window closing on you. Copy and paste that
text into the newsgroup for help.
- Point your browser to http://myipaddress:8000/ and check it out. You
should get an AOLserver introductory page with some links. Also the
telemetry page nstelemetry.adp (which is really nice btw) can run on the
default configuration. I also downloaded it from aolserver.com and placed
it in c:/apps/aolserver34/servers/server1/pages (my installation path was
c:/apps/aolserver34 - yours will probably be in c:/program files/aolserver).
- Note that you can't hit http://localhost:8000/ and expect it to work.
Apparently it doesn't listen on 127.0.0.1 by default.
- You can try this out while running IIS or PWS since AOLserver listens on
port 8000 by default, not the standard port 80. There will be no conflict.
- I was able to immediately make an .adp file in
c:/apps/aolserver34/servers/server1/pages and have it work. I then did a
{load c:/apps/tcl/lib/tclodbc2.2/tclodbc.dll Tclodbc} at the top of that
file, and used that package (nice!), which I already had installed, to
connect to M$ SQL Server and fetch some data into by browser. I'm sure this
is NOT the recommended method of loading a TCL package or library, but it's
the only way I presently know to do it from within AOLserver. (Any help with
that would be appreciated).
- I also used the socket command to connect to a back-end service i'd
written in TCL and fetch some data that way. It worked great except it
locked up AOLserver after a couple minutes of idle time. Probably at thread
cleanup time. ns_sockopen gave the same behavior except it locked up
immediately after the page, no delay. That would be an extremely valuable
thing for a lot of Win users who (like us) have SQL Server data that will
require use of a proxy daemon of some sort running on Win32.
- This was done on window$ NT 4 service pack 6. Should work on any other
win32 version (95 and up).
At this point I'd like to expound some more on issues that Win users would
be interested in, like virtual hosting (parsing Host headers and/or URLs).
But I'm new to AOLserver and still exploring that stuff. In fact if someone
could help me with that topic would be nice. The docs seem to skirt around
some issues that people are likely to be interested in, particularly in
environments like ours where IIS is already in use.
I hope some or all of this can be used. I also hope to run into you guys in
the AIM chat. Thursday 3PM Central Time right? Hope I can get it to work
(first time there).
--
Mark Hubbard: [EMAIL PROTECTED]
Microsoft Certified Professional
Knowledge is Power.
-Original Message-
From: Dossy [EMAIL PROTECTED]
To: [EMAIL PROTECTED] [EMAIL PROTECTED]
Date: Wednesday, August 22, 2001 1:23 PM
Subject: Re: installing AOL Server on WINDOWS!
On 2001.08.22, Mark Hubbard [EMAIL PROTECTED] wrote:
I just did AOLserver last week, from the binaries, not the C source.
Which binaries?
Listers: would you want to see this on the list, or should we keep it in
private email?
The AOLserver walk-through ought to be sent to the list. If nothing
else, a summary of the explanation that could possibly be turned
into or used as a HOWTO. I'd then like to post it to the wiki if
that's okay.
-- Dossy
--
Dossy Shiobara mail: [EMAIL PROTECTED]
Panoptic Computer Network web: http://www.panoptic.com/
Re: [AOLSERVER] installing AOL Server on WINDOWS!
Some helpful info: 1) the documentation seems to be geared toward Unix, I assume some win-centric docs or revisions will come out as popularity grows. in the meantime go to BIN and try nsd -t ..\sample-config.tcl. That's basically what the Start menu shortcut does for you. 2) 3) WinZip (winzip.com) can also be used to open tar, gz, tar.gz, and .tgz files. But I agree WinHelp would be nicer. The TCL man pages are very nice when converted to WinHelp as they are in 8.3 binary release. -Original Message- From: Kerry Barlow [EMAIL PROTECTED] To: [EMAIL PROTECTED] [EMAIL PROTECTED] Date: Wednesday, August 22, 2001 1:55 PM Subject: Re: installing AOL Server on WINDOWS! Dossy: It states in the Admin documentation (http://www.aolserver.com/docs/admin/tech-ch1.htm#20993) to start the server you must type nsd -t nsd.tcl in its simplest form This may work after a user has the system up and configured, however on a new install there is no nsd.tcl file. I did find a sample-config.tcl, however when i type nsd -t sample-config.tcl from the BIN directory the AOlserver says it cannot find the config file. I am guessing I need to enter a path statment in the Windows version. 2) The Online documentation TOC(table of contents) does not work either. if you go to http://www.aolserver.com/docs/admin/admin.htm and click on the TOC icon, you will get a page saying table of contents in a text link (http://www.aolserver.com/docs/index.html) clicking on this link generates an error. [Not Found The requested URL was not found on this server.] 3) Finally there is a Aolserver binary download for Windows based systems. However there is not a downloadable documentation file for Windows. The documentation files are in .tar.gz format. These are not useable on Windows. I suppose there is a convertor program someplace, but why make things difficult for a new user. I believe I came in late on this discussion, it appears like people are attempting to fix these errors I pointed out. At 02:42 PM 8/22/2001 -0400, you wrote: On 2001.08.22, Kerry Barlow [EMAIL PROTECTED] wrote: I am interested in the procedure, considering the online documentation is not accurate. Can you provide a specific example of where it's not accurate? -- Dossy -- Dossy Shiobara mail: [EMAIL PROTECTED] Panoptic Computer Network web: http://www.panoptic.com/ Sincerely Kerry [EMAIL PROTECTED] WWW server hosting Http://mntnweb.com Kerry Barlow p.o. box 21 kirkwood ny 13795
Re: [AOLSERVER] Error Handling
Wow, that is a *great* idea. Then you could register an exception handler for a url path. If it's possible, it would probably have to be something set inside the Tcl interp that is running the ADP or Tcl code, before it starts running the code. Unfortunately I don't yet know enough about Tcl internals to know how to go about doing this, but it is well worth looking into. /s. Is there any way in AOLServer to register an exception handler? What I would like to avoid is going over all the pages in my site and adding a catch statement so that if an exception is thrown, either through the tcl interpreter or or a postgresql query or action, I could catch it with a proc or page. Thanks, Vince
Re: [AOLSERVER] installing AOL Server on WINDOWS!
On 2001.08.22, Kerry Barlow [EMAIL PROTECTED] wrote: Dossy: It states in the Admin documentation (http://www.aolserver.com/docs/admin/tech-ch1.htm#20993) to start the server you must type nsd -t nsd.tcl in its simplest form This may work after a user has the system up and configured, however on a new install there is no nsd.tcl file. I did find a sample-config.tcl, however when i type nsd -t sample-config.tcl from the BIN directory the AOlserver says it cannot find the config file. I am guessing I need to enter a path statment in the Windows version. The sample-config.tcl isn't in the BIN directory, is it? If you're in the bin/ directory, you may need to do: nsd -t ..\sample-config.tcl The documentation is VERY Unix-centric. 2) The Online documentation TOC(table of contents) does not work either. if you go to http://www.aolserver.com/docs/admin/admin.htm and click on the TOC icon, you will get a page saying table of contents in a text link (http://www.aolserver.com/docs/index.html) clicking on this link generates an error. [Not Found The requested URL was not found on this server.] Yeah, the online documentation has suffered from severe bit-rot and neglect. That's why I want to try and get more and more documentation up on the wiki. 3) Finally there is a Aolserver binary download for Windows based systems. However there is not a downloadable documentation file for Windows. The documentation files are in .tar.gz format. These are not useable on Windows. I suppose there is a convertor program someplace, but why make things difficult for a new user. This is going to be a hard one to address, unless there's a nice tool out there that can convert from nroff to Windows Help format, which I think there is ... Currently, the help files are all HTML format, and any Windows user can go out and download WinZip which can easily handle .tar.gz format. But yes, the average Windows user isn't going to know this, I guess. I believe I came in late on this discussion, it appears like people are attempting to fix these errors I pointed out. We're always trying to improve things. It's just hard when people tell us that there are problems but don't tell us exactly what those problems are... Thanks for taking the time to point out exactly what needs to be addressed! Perhaps it's time I created the AOLserver Quickstart Guide page on the wiki ... -- Dossy -- Dossy Shiobara mail: [EMAIL PROTECTED] Panoptic Computer Network web: http://www.panoptic.com/
Re: [AOLSERVER] Error Handling
Yes it is. If we end up using AOLserver, we will require something like that. If it can't do it, I'll be writing a parser (in TCL) for our pages that will do it. -- Mark Hubbard: [EMAIL PROTECTED] Microsoft Certified Professional Knowledge is Power. -Original Message- From: Scott Goodwin [EMAIL PROTECTED] To: [EMAIL PROTECTED] [EMAIL PROTECTED] Date: Wednesday, August 22, 2001 2:04 PM Subject: Re: Error Handling Wow, that is a *great* idea. Then you could register an exception handler for a url path. If it's possible, it would probably have to be something set inside the Tcl interp that is running the ADP or Tcl code, before it starts running the code. Unfortunately I don't yet know enough about Tcl internals to know how to go about doing this, but it is well worth looking into. /s. Is there any way in AOLServer to register an exception handler? What I would like to avoid is going over all the pages in my site and adding a catch statement so that if an exception is thrown, either through the tcl interpreter or or a postgresql query or action, I could catch it with a proc or page. Thanks, Vince
Re: [AOLSERVER] Error Handling / post-processing
Along the same lines, is there a way to capture all the output from an ADP in a buffer, and then alter it before it's transmitted? This would allow things that can't be done easily, or at all, in IIS/ASP. -- Mark Hubbard: [EMAIL PROTECTED] Microsoft Certified Professional Knowledge is Power. -Original Message- From: Scott Goodwin [EMAIL PROTECTED] To: [EMAIL PROTECTED] [EMAIL PROTECTED] Date: Wednesday, August 22, 2001 2:04 PM Subject: Re: Error Handling Wow, that is a *great* idea. Then you could register an exception handler for a url path. If it's possible, it would probably have to be something set inside the Tcl interp that is running the ADP or Tcl code, before it starts running the code. Unfortunately I don't yet know enough about Tcl internals to know how to go about doing this, but it is well worth looking into. /s. Is there any way in AOLServer to register an exception handler? What I would like to avoid is going over all the pages in my site and adding a catch statement so that if an exception is thrown, either through the tcl interpreter or or a postgresql query or action, I could catch it with a proc or page. Thanks, Vince
Re: [AOLSERVER] Error Handling / post-processing
+-- On Aug 22, Mark Hubbard said: Along the same lines, is there a way to capture all the output from an ADP in a buffer, and then alter it before it's transmitted? This would allow things that can't be done easily, or at all, in IIS/ASP. Register your own Tcl proc for /*.adp. Use ns_adp_parse to process the ADP, then alter the result as necessary, then ns_return the altered string.
Re: [AOLSERVER] installing AOL Server on WINDOWS!
On 2001.08.22, Mark Hubbard [EMAIL PROTECTED] wrote:
- I was able to immediately make an .adp file in
c:/apps/aolserver34/servers/server1/pages and have it work. I then did a
{load c:/apps/tcl/lib/tclodbc2.2/tclodbc.dll Tclodbc} at the top of that
file, and used that package (nice!), which I already had installed, to
connect to M$ SQL Server and fetch some data into by browser. I'm sure this
is NOT the recommended method of loading a TCL package or library, but it's
the only way I presently know to do it from within AOLserver. (Any help with
that would be appreciated).
Why are you using tclodbc to connect to MS SQL Server? Would you
be interested in trying out my nsfreetds database driver?
http://panoptic.com/wiki/aolserver/nsfreetds
Yes, it is still very experimental, but it does work (lightly
tested) on several platforms.
Checking the FreeTDS site, I don't see any mention of freetds
building on Win32. Hmm, that could be a problem.
If you're interested in exploring the possibilities, I'll offer
any help I can.
At this point I'd like to expound some more on issues that Win users would
be interested in, like virtual hosting (parsing Host headers and/or URLs).
nsvhr setup on Win32 should be no different than on other platforms,
or maybe I'm mistaken.
-- Dossy
--
Dossy Shiobara mail: [EMAIL PROTECTED]
Panoptic Computer Network web: http://www.panoptic.com/
Re: [AOLSERVER] installing AOL Server on WINDOWS!
Yes! I'm dying to try it out! My test copy of AOLserver is on Win32, but
the real point for us is to get it running on our Linux boxes as well. I'm
not as skilled at installing configuring new programs there, and
definitely not when they have to be compiled from C. Do you have a binary
that is compatible with Red Hat Linux 7.0 or 7.1? If not be prepared for
some hand-holding on the C make.
Also do you have an URL for a nsvhr setup doc? I don't know where to begin
on that. But it's a make-or-break issue for us, and a lot of other
companies I'm sure. Any experience I get from doing it on Windows will be
contrib'd back to the group.
--
Mark Hubbard: [EMAIL PROTECTED]
Microsoft Certified Professional
Knowledge is Power.
-Original Message-
From: Dossy [EMAIL PROTECTED]
To: [EMAIL PROTECTED] [EMAIL PROTECTED]
Date: Wednesday, August 22, 2001 2:16 PM
Subject: Re: installing AOL Server on WINDOWS!
On 2001.08.22, Mark Hubbard [EMAIL PROTECTED] wrote:
- I was able to immediately make an .adp file in
c:/apps/aolserver34/servers/server1/pages and have it work. I then did a
{load c:/apps/tcl/lib/tclodbc2.2/tclodbc.dll Tclodbc} at the top of that
file, and used that package (nice!), which I already had installed, to
connect to M$ SQL Server and fetch some data into by browser. I'm sure
this
is NOT the recommended method of loading a TCL package or library, but
it's
the only way I presently know to do it from within AOLserver. (Any help
with
that would be appreciated).
Why are you using tclodbc to connect to MS SQL Server? Would you
be interested in trying out my nsfreetds database driver?
http://panoptic.com/wiki/aolserver/nsfreetds
Yes, it is still very experimental, but it does work (lightly
tested) on several platforms.
Checking the FreeTDS site, I don't see any mention of freetds
building on Win32. Hmm, that could be a problem.
If you're interested in exploring the possibilities, I'll offer
any help I can.
At this point I'd like to expound some more on issues that Win users
would
be interested in, like virtual hosting (parsing Host headers and/or
URLs).
nsvhr setup on Win32 should be no different than on other platforms,
or maybe I'm mistaken.
-- Dossy
--
Dossy Shiobara mail: [EMAIL PROTECTED]
Panoptic Computer Network web: http://www.panoptic.com/
Re: [AOLSERVER] installing AOL Server on WINDOWS!
THe sample-config.tcl in 3.4x is not totally correct either. I have already found a couple of parameters in the wrong section and it has delayed our conversion from 2.3.3 until I can go through the source and figure out ALL of the parameters and which section they should go in. Maybe the docs are correct - I dunno - but I don't really trust them. I'll post results somewhere when I'm done. If someone else has already done this and can forward it, that'd be cool. Jim On 2001.08.22, Kerry Barlow [EMAIL PROTECTED] wrote: Dossy: It states in the Admin documentation (http://www.aolserver.com/docs/admin/tech-ch1.htm#20993) to start the server you must type nsd -t nsd.tcl in its simplest form This may work after a user has the system up and configured, however on a new install there is no nsd.tcl file. I did find a sample-config.tcl, however when i type nsd -t sample-config.tcl from the BIN directory the AOlserver says it cannot find the config file. I am guessing I need to enter a path statment in the Windows version. The sample-config.tcl isn't in the BIN directory, is it? If you're in the bin/ directory, you may need to do: nsd -t ..\sample-config.tcl The documentation is VERY Unix-centric. 2) The Online documentation TOC(table of contents) does not work either. if you go to http://www.aolserver.com/docs/admin/admin.htm and click on the TOC icon, you will get a page saying table of contents in a text link (http://www.aolserver.com/docs/index.html) clicking on this link generates an error. [Not Found The requested URL was not found on this server.] Yeah, the online documentation has suffered from severe bit-rot and neglect. That's why I want to try and get more and more documentation up on the wiki. 3) Finally there is a Aolserver binary download for Windows based systems. However there is not a downloadable documentation file for Windows. The documentation files are in .tar.gz format. These are not useable on Windows. I suppose there is a convertor program someplace, but why make things difficult for a new user. This is going to be a hard one to address, unless there's a nice tool out there that can convert from nroff to Windows Help format, which I think there is ... Currently, the help files are all HTML format, and any Windows user can go out and download WinZip which can easily handle .tar.gz format. But yes, the average Windows user isn't going to know this, I guess. I believe I came in late on this discussion, it appears like people are attempting to fix these errors I pointed out. We're always trying to improve things. It's just hard when people tell us that there are problems but don't tell us exactly what those problems are... Thanks for taking the time to point out exactly what needs to be addressed! Perhaps it's time I created the AOLserver Quickstart Guide page on the wiki ... -- Dossy -- Dossy Shiobara mail: [EMAIL PROTECTED] Panoptic Computer Network web: http://www.panoptic.com/
Re: [AOLSERVER] Error Handling
We do this. Register a proc for /dir, put your TCL scripts there, in the /dir handler look at the URL suffix and do a TCL source command or ns_returnfile. (Put a catch around the source command - that's the important part). Jim Wow, that is a *great* idea. Then you could register an exception handler for a url path. If it's possible, it would probably have to be something set inside the Tcl interp that is running the ADP or Tcl code, before it starts running the code. Unfortunately I don't yet know enough about Tcl internals to know how to go about doing this, but it is well worth looking into. /s. Is there any way in AOLServer to register an exception handler? What I would like to avoid is going over all the pages in my site and adding a catch statement so that if an exception is thrown, either through the tcl interpreter or or a postgresql query or action, I could catch it with a proc or page. Thanks, Vince
Re: [AOLSERVER] Error Handling
At 12:33 PM 8/22/01, you wrote: We do this. Register a proc for /dir, put your TCL scripts there, in the /dir handler look at the URL suffix and do a TCL source command or ns_returnfile. (Put a catch around the source command - that's the important part). Jim I think an important thing to remember is what the suggestions from Jim, Rob allude to: there are already many paths within AOLserver (and even more if you include the ACS) for serving files. Within AOLserver, there are different paths for serving .tcl, .adp, and static files. You presumably don't need too much error handling around the static files, but I believe your .tcl and .adp files will have different solutions required for each. Plus, I don't believe the suggestions already mentioned will catch errors in registered filters. But! This is good stuff, so let me encourage you to continue! Jerry = Jerry Asher [EMAIL PROTECTED] 1678 Shattuck Avenue Suite 161Tel: (510) 549-2980 Berkeley, CA 94709Fax: (877) 311-8688
Re: [AOLSERVER] Error Handling
Yes. We do virtual hosting this way. Register a proc for /, look at the Host: header and URL, then source/read the files from whatever directory you want. The downside is that you are invoking TCL on every request, which has some overhead. But we've been doing it for years, have 1M+ hits/day, and our server is mostly idle. You could also do the same thing with a C extension (and there is one already available somewhere...) We've found that using TCL is easier, safer, and has excellent performance characteristics. Jim Excellent. Could this technique also be used to, say, set your PageRoot based on the request URL, or maybe a Host header? Maybe not the real PageRoot could be set, but maybe a falsified or virtualized one? -- Mark Hubbard: [EMAIL PROTECTED] Microsoft Certified Professional Knowledge is Power. -Original Message- From: Jim Wilcoxson [EMAIL PROTECTED] To: [EMAIL PROTECTED] [EMAIL PROTECTED] Date: Wednesday, August 22, 2001 2:31 PM Subject: Re: Error Handling We do this. Register a proc for /dir, put your TCL scripts there, in the /dir handler look at the URL suffix and do a TCL source command or ns_returnfile. (Put a catch around the source command - that's the important part). Jim Wow, that is a *great* idea. Then you could register an exception handler for a url path. If it's possible, it would probably have to be something set inside the Tcl interp that is running the ADP or Tcl code, before it starts running the code. Unfortunately I don't yet know enough about Tcl internals to know how to go about doing this, but it is well worth looking into. /s. Is there any way in AOLServer to register an exception handler? What I would like to avoid is going over all the pages in my site and adding a catch statement so that if an exception is thrown, either through the tcl interpreter or or a postgresql query or action, I could catch it with a proc or page. Thanks, Vince
Re: [AOLSERVER] installing AOL Server on WINDOWS!
Mark, I missed the original message, but you seem interested in ODBC to SQL Server from Windows and UNIX? Is there some reason you can't use nsodbc, or the odbc driver I've built? (http://theashergroup.com/download). I recall hearing that nsodbc will build on windows, and I am pretty sure I got my driver building on windows. They both work on linux, but you need some form of ODBC Manager. You can find some nsvhr setup guides at http://theashergroup/tag/articles/. In the windows case, it should go without saying to use nsvhr/nssock and not nsvhr/nsunix. By the way, on linux, I now have evidence that nsvhr/nssock is much much faster than using Apache's reverse proxying solution. I don't know which is faster on Windows. Jerry = Jerry Asher [EMAIL PROTECTED] 1678 Shattuck Avenue Suite 161Tel: (510) 549-2980 Berkeley, CA 94709Fax: (877) 311-8688
Re: [AOLSERVER] Error Handling
Yes! Thank you! That elusive bit of info will clear a major roadblock to adopting AOLS. I've been puzzling over why the nsvhr and those other modules are needed, if that can be done instead. I guess the C modules would be good for a REALLY high traffic site. But that wouldn't be us. I also agree with what Jerry said earlier. The many paths through the server, and the many hooks into its processing steps, are what make it attractive. More software should be like that. -- Mark Hubbard: [EMAIL PROTECTED] Microsoft Certified Professional Knowledge is Power. -Original Message- From: Jim Wilcoxson [EMAIL PROTECTED] To: [EMAIL PROTECTED] [EMAIL PROTECTED] Date: Wednesday, August 22, 2001 2:59 PM Subject: Re: Error Handling Yes. We do virtual hosting this way. Register a proc for /, look at the Host: header and URL, then source/read the files from whatever directory you want. The downside is that you are invoking TCL on every request, which has some overhead. But we've been doing it for years, have 1M+ hits/day, and our server is mostly idle. You could also do the same thing with a C extension (and there is one already available somewhere...) We've found that using TCL is easier, safer, and has excellent performance characteristics. Jim Excellent. Could this technique also be used to, say, set your PageRoot based on the request URL, or maybe a Host header? Maybe not the real PageRoot could be set, but maybe a falsified or virtualized one? -- Mark Hubbard: [EMAIL PROTECTED] Microsoft Certified Professional Knowledge is Power. -Original Message- From: Jim Wilcoxson [EMAIL PROTECTED] To: [EMAIL PROTECTED] [EMAIL PROTECTED] Date: Wednesday, August 22, 2001 2:31 PM Subject: Re: Error Handling We do this. Register a proc for /dir, put your TCL scripts there, in the /dir handler look at the URL suffix and do a TCL source command or ns_returnfile. (Put a catch around the source command - that's the important part). Jim Wow, that is a *great* idea. Then you could register an exception handler for a url path. If it's possible, it would probably have to be something set inside the Tcl interp that is running the ADP or Tcl code, before it starts running the code. Unfortunately I don't yet know enough about Tcl internals to know how to go about doing this, but it is well worth looking into. /s. Is there any way in AOLServer to register an exception handler? What I would like to avoid is going over all the pages in my site and adding a catch statement so that if an exception is thrown, either through the tcl interpreter or or a postgresql query or action, I could catch it with a proc or page. Thanks, Vince
Re: [AOLSERVER] installing AOL Server on WINDOWS!
I looked into the nsodbc -- odbc manager -- odbc-driver-for-mssql solution. Some of those 3 components already exist on Win32, and we'd like a uniform solution for both platforms. It seemed very suitable, except that I couldn't locate Linux binaries for any of those components. (I have no success thus far at compiling C). And the only sources I could find for a SQL Server ODBC driver require the Sybase Client Libraries to compile (whatever that is). I also considered using JDBC object to connect to SQL, and then scripting those through TclBlend. Or FreeTDS if I could get it built and configured. Or the ODBC-ODBC Bridge from EasySoft. Or a home-grown RPC daemon on a Win32 box just to handle the SQL Server. Or just installing Oracle (that is, until I saw the price tag). Thanks for any help in this situation. If we can adopt AOLserver in some form (which means hooking it to SQL Server) I can start contributing software and tech help to the community. -- Mark Hubbard: [EMAIL PROTECTED] Microsoft Certified Professional Knowledge is Power. -Original Message- From: Jerry Asher [EMAIL PROTECTED] To: [EMAIL PROTECTED] [EMAIL PROTECTED] Date: Wednesday, August 22, 2001 3:05 PM Subject: Re: installing AOL Server on WINDOWS! Mark, I missed the original message, but you seem interested in ODBC to SQL Server from Windows and UNIX? Is there some reason you can't use nsodbc, or the odbc driver I've built? (http://theashergroup.com/download). I recall hearing that nsodbc will build on windows, and I am pretty sure I got my driver building on windows. They both work on linux, but you need some form of ODBC Manager. You can find some nsvhr setup guides at http://theashergroup/tag/articles/. In the windows case, it should go without saying to use nsvhr/nssock and not nsvhr/nsunix. By the way, on linux, I now have evidence that nsvhr/nssock is much much faster than using Apache's reverse proxying solution. I don't know which is faster on Windows. Jerry = Jerry Asher [EMAIL PROTECTED] 1678 Shattuck Avenue Suite 161Tel: (510) 549-2980 Berkeley, CA 94709Fax: (877) 311-8688
Re: [AOLSERVER] Error Handling
At 01:21 PM 8/22/01, you wrote: Yes! Thank you! That elusive bit of info will clear a major roadblock to adopting AOLS. I've been puzzling over why the nsvhr and those other modules are needed, if that can be done instead. I guess the C modules would be good for a REALLY high traffic site. But that wouldn't be us. Regarding multiple paths as regards virtual hosting. I find both the simple Tcl and the C based virtual hosting techniques have their uses, it depends on what you are trying to do. nsvhr is really a port 80 multiplexer. It lets you seamlessly integrate all sorts of technology into your webservice, at the same time presenting these services to your client on port 80. That both looks nice as well as helps you get past firewalls. But what I really like about nsvhr is that if one aolserver site goes down (and they do at times) that it doesn't take any of your other sites down. This can happen do to AOLserver bugs that haven't been fixed that some one site exploits, or maybe because one site needs to use an as yet experimental module. I've found nsvhr itself to be very stable (modulo the bugs I occasionally put into it.) One shortcoming of AOLserver 3 (rectified in AOLserver 4) is that Tcl based AOLservers all share the same Tcl libraries. So if you want one site to use say library version 1 of TclFOO, and another site wants to use library version 2 of TclFOO, you can't do that. This can lead to site upgrade difficulties when you have lots of sites. If you want to be an ISP that offers thousands of sites that are mainly static pages, CGI, or use a fixed set of Tcl procs that you provide, then Tcl based virtual hosting is what you want. If you want to piece together a complex webservice than you may wish to use an nsvhr/apache/squid reverse proxying solution. Regarding speed, as Jim mention's he's had no problems with up to a million hits using Tcl procs. Recent testing of mine (http://www.theashergroup.com/tag/articles/reverse-proxies/vhr-benchmarks_files/connection-performance.adp) demonstrate that an nsvhr/nssock solution can handle more than 900,000 hits per hour (of a 2K file) (on linux) and about 2.5 million hits per day of nothing but 32K bytes files. Jerry = Jerry Asher [EMAIL PROTECTED] 1678 Shattuck Avenue Suite 161Tel: (510) 549-2980 Berkeley, CA 94709Fax: (877) 311-8688
Re: [AOLSERVER] installing AOL Server on WINDOWS!
Or the ODBC-ODBC Bridge from EasySoft. I have about three weeks experience with the ODBC-ODBC bridge, and it works well and seemed to work pretty simply. It's what I used when converting Rob's DB/2 driver into the new odbc driver. If I recall correctly, that would give you the possibilities of: Windows: AOLserver speaking ODBC to Windows ODBC Manager to SQL Server or Linux: AOLserver speaking ODBC to Linux: Easy Soft Bridge to Windows: SQL Server or even Linux: AOLserver speaking ODBC to Windows: Easy Soft Bridge to Windows: SQL Server Unfortunately within an AOLserver application, your choice of db and db driver can impact what your code looks like. The advantage of any of the above is that you will only have to debug/experience one db driver within AOLserver, regardless of which platform you run AOLserver on. A client of mine found that AOLserver connecting to SQL Server didn't have the performance they desired. And I believe that others have described experiences where AOLserver on Windows just didn't have the punch of AOLserver on *nix. If Linux is a possibility in the future, you may wish to consider using it now or benchmarking it. Also, another choice you may wish to look into now if Linux is a future migration path is using Postgres instead of SQL Server. Postgres runs on both Linux and Windows, and that will also give you more options when it comes to migrating webserver or db from one platform to another. You'll be able to do all sorts of stuff without having to worry about changing dbs, or changing your applications. I can't comment on which is faster for your needs: postgres or sql server. Jerry = Jerry Asher [EMAIL PROTECTED] 1678 Shattuck Avenue Suite 161Tel: (510) 549-2980 Berkeley, CA 94709Fax: (877) 311-8688
Re: [AOLSERVER] Error Handling
Thanks for the info. I'm reading your howto right now. Sounds like the C modules will be a good solution for later, after we really have lots of sites on AOLserver. For now I think the all-TCL register a proc on / solution will work, as long as we don't have trouble with AOLserver hanging, as I've done many times already using ns_sockopen. -- Mark Hubbard: [EMAIL PROTECTED] Microsoft Certified Professional Knowledge is Power. -Original Message- From: Jerry Asher [EMAIL PROTECTED] To: [EMAIL PROTECTED] [EMAIL PROTECTED] Date: Wednesday, August 22, 2001 3:37 PM Subject: Re: Error Handling At 01:21 PM 8/22/01, you wrote: Yes! Thank you! That elusive bit of info will clear a major roadblock to adopting AOLS. I've been puzzling over why the nsvhr and those other modules are needed, if that can be done instead. I guess the C modules would be good for a REALLY high traffic site. But that wouldn't be us. Regarding multiple paths as regards virtual hosting. I find both the simple Tcl and the C based virtual hosting techniques have their uses, it depends on what you are trying to do. nsvhr is really a port 80 multiplexer. It lets you seamlessly integrate all sorts of technology into your webservice, at the same time presenting these services to your client on port 80. That both looks nice as well as helps you get past firewalls. But what I really like about nsvhr is that if one aolserver site goes down (and they do at times) that it doesn't take any of your other sites down. This can happen do to AOLserver bugs that haven't been fixed that some one site exploits, or maybe because one site needs to use an as yet experimental module. I've found nsvhr itself to be very stable (modulo the bugs I occasionally put into it.) One shortcoming of AOLserver 3 (rectified in AOLserver 4) is that Tcl based AOLservers all share the same Tcl libraries. So if you want one site to use say library version 1 of TclFOO, and another site wants to use library version 2 of TclFOO, you can't do that. This can lead to site upgrade difficulties when you have lots of sites. If you want to be an ISP that offers thousands of sites that are mainly static pages, CGI, or use a fixed set of Tcl procs that you provide, then Tcl based virtual hosting is what you want. If you want to piece together a complex webservice than you may wish to use an nsvhr/apache/squid reverse proxying solution. Regarding speed, as Jim mention's he's had no problems with up to a million hits using Tcl procs. Recent testing of mine (http://www.theashergroup.com/tag/articles/reverse-proxies/vhr-benchmarks_f iles/connection-performance.adp) demonstrate that an nsvhr/nssock solution can handle more than 900,000 hits per hour (of a 2K file) (on linux) and about 2.5 million hits per day of nothing but 32K bytes files. Jerry = Jerry Asher [EMAIL PROTECTED] 1678 Shattuck Avenue Suite 161Tel: (510) 549-2980 Berkeley, CA 94709Fax: (877) 311-8688
Re: [AOLSERVER] Error Handling
In a message dated 8/22/01 2:55:07 PM Eastern Daylight Time, [EMAIL PROTECTED]
writes:
Is there any way in AOLServer to register an exception handler? What I
would like to avoid is going over all the pages in my site and adding
a catch statement so that if an exception is thrown, either through the
tcl interpreter or or a postgresql query or action, I could catch it with a
proc or page.
You could also simply put a catch in your startpage around the include.
%
if {[catch {
ns_adp_include [ns_url2file [ns_conn url]]
} err]} {
ns_adp_puts An error occurred: $err
# or whatever else you wanna do with the error
}
%
-- michael
___
michael richman
sr. software engineer
aol local technology
214.954.6204
Re: [AOLSERVER] installing AOL Server on WINDOWS!
Also do you have an URL for a nsvhr setup doc? I don't know where to begin on that. But it's a make-or-break issue for us, and a lot of other companies I'm sure. Any experience I get from doing it on Windows will be contrib'd back to the group. To the best of my knowledge nsvhr as present in AOLServer CVS tree doesn't even compile under windows so unless you can fix it (which is not hard) you won't get it. The only known (to me) place you can get nsvhr under windows is in my own private fork of AOLServer 4 beta available here: http://acs-misc.sourceforge.net/ns_rel_beta2.html It also has nsxml, nspostgres, nscache and nssha1. Don't use it for production work. You've been warned.
Re: [AOLSERVER] installing AOL Server on WINDOWS!
Tell you what, I can walk you through that if you'll walk me through the same thing with PostGreSQL. I just did AOLserver last week, from the binaries, not the C source. If you need to compile it from the source I can't help you. I have battle-tested info on installing PostgresSQL on Windows here: http://acs-misc.sourceforge.net/acs3xwin.html (part of it). If you try it and it doesn't work, tell me about (although I did at least 2 installs from scratch following my own instructions). The only thing is that if you want to access it from AOLServer on Windows, you need to have nspostgres module and supporting *dll which, to the best of my knowledge, aren't available in a nice package except for this place: http://acs-misc.sourceforge.net/ns_rel_beta2.html
[AOLSERVER] foo.tcl doesn't seem to work
I've installed AOLServer V3.4. I think I've setup ora8.so with it. Now, I'm trying to test with table-test.tcl that comes standard with the oracle driver. However, the page shows up as just html, including ns_write strings. It seems like it doesn't do any tcl execution. So, I put the following in the config file: ns_section ns/server/server1/tcl ns_param Debug On ns_param Library /ria/usr/local/aolserver/modules/tcl # I did try /ria/usr/local/aolserver/servers/server1/modules/tcl with no luck What am I missing? Where can I find step-by-step instructions on how to do this (the standard doc. seems a little terse for a beginner, even on other issues that I'm struggling with like configuration)? Thanks Sanju.
[AOLSERVER] 'moved pages' redirects?
What is the correct way of sending a permanent redirect when visitors (or spiders) visit old URLs of pages that have moved to different spots in the tree? Is registering a procedure for the old pages, and having it write out the redirect the best way?
Re: [AOLSERVER] 'moved pages' redirects?
That's the way I do it. Michael Jim Tittsler wrote: What is the correct way of sending a permanent redirect when visitors (or spiders) visit old URLs of pages that have moved to different spots in the tree? Is registering a procedure for the old pages, and having it write out the redirect the best way?
Re: [AOLSERVER] installing AOL Server on WINDOWS!
hello! thanx for ur response. I'm a bit busy. will send u the details of postgresql soon. coz I'll have to spend some time on it. I 'll try in the afternoon. curegards --- Mark Hubbard [EMAIL PROTECTED] wrote: Tell you what, I can walk you through that if you'll walk me through the same thing with PostGreSQL. I just did AOLserver last week, from the binaries, not the C source. If you need to compile it from the source I can't help you. Listers: would you want to see this on the list, or should we keep it in private email? -- Mark Hubbard: [EMAIL PROTECTED] Microsoft Certified Professional Knowledge is Power. -Original Message- From: rana deepti [EMAIL PROTECTED] To: [EMAIL PROTECTED] [EMAIL PROTECTED] Date: Wednesday, August 22, 2001 6:44 AM Subject: installing AOL Server on WINDOWS! hello! I'm very new to AOLServer. At present my application is in TOMCAT. I've installed postgresql on windows successfully. Now I want to use AOLServer with it. but I'm not able to find a good documentation or article at HOW TO INSTALL AOL SERVER ON WINDOWS I mean complete steps guide can any one help me? thanx in advance regards...deepti __ Do You Yahoo!? Make international calls for as low as $.04/minute with Yahoo! Messenger http://phonecard.yahoo.com/ __ Do You Yahoo!? Make international calls for as low as $.04/minute with Yahoo! Messenger http://phonecard.yahoo.com/
