From: Bear Giles <[EMAIL PROTECTED]>
bear> > This requires the API to stay
bear> > the same except for added functions, and for types and structures to
bear> > never change (except for adding new types and new structures).
bear>
bear> But the flip side, which is what I was referring to, is when the
bear> framework tries to use those new functions. It needs to determine
bear> that the new functions aren't present in a legacy plug-in and somehow
bear> invalidate any calls to them.
Ah, that's what you meant. Of course, but that part is comparatively
trivial.
bear> In contrast, with a plug-in the framework itself acts as the loader,
bear> and it must detect mising symbols in older shared libraries. Depending
bear> on the way it's hooked, it either has to resolve each symbol individually
bear> or a single structure and then check the version number.
The way we've done it with the ENGINE framework is that the engine
itself has to tell libcrypto exactly what functionality it offers.
--
Richard Levitte \ Spannvägen 38, II \ [EMAIL PROTECTED]
Redakteur@Stacken \ S-168 35 BROMMA \ T: +46-8-26 52 47
\ SWEDEN \ or +46-733-72 88 11
Procurator Odiosus Ex Infernis -- [EMAIL PROTECTED]
Member of the OpenSSL development team: http://www.openssl.org/
Software Engineer, GemPlus: http://www.gemplus.com/
Unsolicited commercial email is subject to an archival fee of $400.
See <http://www.stacken.kth.se/~levitte/mail/> for more info.
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
