[EMAIL PROTECTED] (David N. Welton) writes: > How about creating a rivetApacheCompat.c file?
I don't know... Apache is pretty tightly coupled to Rivet. There are a *lot* of places where the ap_ functions are used. In the file upload code, for instance, and in a lot of places in rivetCore.c > If we aren't compiling as an Apache module, we compile that and use > its code? For the moment, I am a bit dubious about the idea of putting the EscapeURL stuff in without basing it on the Apache API. It's a waste of space, for the moment. On the other hand, I do agree with the goal of being able to create an independant binary. However, that's not going to be an easy process, and I think we need to go about it with a comprehensive plan. -- 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/
