Damon Courtney <[EMAIL PROTECTED]> writes: > > [EMAIL PROTECTED] writes:
> > > -set APXS "apxs" > > > +set APXS "/usr/local/apache/bin/apxs" > > Hrm... add it to your path? Or is there a better way? > Actually, this is the best solution. On a standard Apache > install, this is where APXS will be. Yuck. > Anyplace else is not standard. So, at least it gives the user the > general idea if they edit the file. By just putting APXS, some > users might not understand that the variable should be a full path > to the APXS script. Maybe we should have a better warning message then. A *lot* of people (namely, anyone with a Linux box with Apache installed as part of their distribution) will have apxs in a 'non-standard' location. Either that, or do some checking to see if we can find it. > By setting the aborted variable in the Apache connection, the page > immediately halts sending any and all data to the user. Now, yes, the > script does continue executing, but that can't be helped just yet. We > should find some way to fix that really. Exit is bad, because it > quite literally causes the Apache child process to exit. This can be > VERY expensive in terms of having to continually restart children. > If you have any ideas, I'm open to hearing them. In the > meantime, this at least works quite well. 0-] Ok... just be sure to put in the docs that "*it DOES NOT stop execution of the Tcl script*", otherwise people will send us weird errors! I've been thinking about this lately, as I have a mod_dtcl user who is trying to 'exit' from .ttml pages, but can't find a good way to do so. I haven't been able to come up with a good answer, so far:-/ -- David N. Welton Consulting: http://www.dedasys.com/ Free Software: http://people.debian.org/~davidw/ Apache Tcl: http://tcl.apache.org/ Personal: http://www.efn.org/~davidw/
