httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Randy Terbush" <ra...@covalent.net>
Subject RE: binary backwards compatability.
Date Thu, 30 Mar 2000 17:51:28 GMT
Actually Ryan's idea of ap_sizeof(token).

> -----Original Message-----
> From: William A. Rowe, Jr. [mailto:wrowe@lnd.com]
> Sent: Thursday, March 30, 2000 9:32 AM
> To: new-httpd@apache.org
> Subject: RE: binary backwards compatability.
> 
> 
> > 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.
> 
> Right there, I think you hit it.  No 'extra space' on structures,
> implement Randy's idea of a ap_sizeof(token) (not another string
> compare, _please_!)  Or a constant ap_sizeof_server_rec_t.  And,
> how about a 8 byte token, each arg in a byte.  Start, for a three
> byte token, of {1, 2, 3, 0, 0, 0, 0, 0).  (It could be much more
> sophisticated, of course).  If the type _OR_ the meaning of the
> first arg changes, then the next build carries (4, 2, 1, [...]).
> 
> 

Mime
View raw message