> -----Original Message-----
> From: jon * [SMTP:[EMAIL PROTECTED]]
>
> > Also, a potentially dumb question: is there a forseeable time when
> Apache and
> > JServ do not have to move in lock step? That is, when I can just install
> version
> > 1.x of JServ and continually upgrade my versions of Apache w/o having to
> worry
> > about things like mod_jserv.c compatibilities -- maybe a better way to
> ask
> this
> > is, what is the need to associate JServ with distinct versions of
> Apache?
>
> This is a result of the way that .dll's work. Send all of your complaints
> to
> M$ or get a unix box and quit shelling out money for crappy software that
> you don't even have the source to.
> <smile>
>
The Windows version of Apache is built with a .DEF file (starting
with v.1.3.4 I believe), and therefore I think the problem to which you're
referring (mis-alignment of function index #'s) is no longer an issue.
<flame bait>Frankly, I think that dynamic linking on Windows is
superior to dynamic linking on Linux, just try creating an Apache module on
Linux that dynamically links to a JVM and you'll see what I mean.</flame
bait>
What I've noticed is that Apache requires the version number built
into the module to EXACTLY match the version of Apache that you are using.
Therefore it seems that modules are required to be built specifically for
the version of Apache that you are using. This seems to be true on Linux as
well as Windows. When I haven't rebuilt my modules specifically for the
version of Apache that I'm using I get a "this module not compatible" error
from Apache. When I recompile the problem goes away.
I also would like to know if there's a way to avoid this.
ted stockwell
----------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/main/mail.html/>
Problems?: [EMAIL PROTECTED]
