> [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. 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.
> > +TCL_CMD_HEADER( Rivet_AbortPageCmd )
> > +{
> > + rivet_interp_globals *globals = Tcl_GetAssocData(interp, "rivet",
> > NULL);
> > + rivet_server_conf *rsc =
> > + RIVET_SERVER_CONF( globals->r->server->module_config );
> > +
> > + if (objc != 1)
> > + {
> > + Tcl_WrongNumArgs(interp, 1, objv, "");
> > + return TCL_ERROR;
> > + }
> > +
> > + Rivet_PrintHeaders(globals->r);
> > + Tcl_Flush(*(rsc->outchannel));
> > +
> > + globals->r->connection->aborted = 1;
> > +
> > + return TCL_OK;
> > +}
>
> Hey, this is cool - how does it work, exactly? It doesn't stop the
> script from executing, it just cuts off the page when it is called?
> Still not quite 'exit', but better than anything I've got so far.
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-]
D
