httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ben Laurie <...@algroup.co.uk>
Subject Re: binary backwards compatability.
Date Thu, 30 Mar 2000 20:43:46 GMT
rbb@apache.org wrote:
> 
> > > But of course it can know... the module vendor has seen the source changes
> > > and knows if they can continue to release their version for the new Apache
> > > server version. As it stands, Apache decides for them.  Your making an
> > > assumption that the module has no knowledge of the changes in the server.
> >
> > We're talking about binaries here. A given binary module definitely has no
> > knowledge about *future* changes in the server. Therefore, if the MAJOR
> > has been updated, then then binary module simply cannot run -- request_rec
> > may have been obsoleted for all it knows.
> 
> You are correct, it cannot KNOW.  However, the module can make a damn good
> guess.  The module can look at what arguments are being passed to the
> functions it uses, and if they match up with what the module expects to
> see, that is a pretty good good indicator that the function hasn't broken
> the module.  The module could also check the size of the major structures
> (request_rec, server_rec, connection_rec), and get a good indication of
> whether it can still run.
> 
> Is this perfect, no of course not.  But it is better than having the
> server say "If you weren't compiled for this exact version of the server,
> I don't support you"

Well, you can add version numbers to each structure. And even each API.
But why? This is free software. We got the source, Luke. Why jump
through hoops to support the old-fangled way of doing things?

Cheers,

Ben.

--
http://www.apache-ssl.org/ben.html

Mime
View raw message