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
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
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
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.
+-- 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
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
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
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,
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
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.
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
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
12 matches
Mail list logo
