[1871] in Kerberos_V5_Development
Re: krb5-libs/66: add API versioning before next release
daemon@ATHENA.MIT.EDU (Barry Jaspan)
Wed Oct 23 15:22:35 1996
Date: Wed, 23 Oct 1996 15:22:21 -0400
From: "Barry Jaspan" <bjaspan@MIT.EDU>
To: epeisach@MIT.EDU
Cc: krbdev@MIT.EDU, krb5-bugs@MIT.EDU
In-Reply-To: <9610231908.AA06440@kangaroo.mit.edu> (message from Ezra Peisach
on Wed, 23 Oct 1996 15:08:23 EDT)
We have a number of "functions" that are handled by dispatch tables in
krb5.hin (i.e. krb5_encrypt, krb5_cc_*, krb5_rc_*) - should these
be proper functions as well - or will a dispatch table be
sufficient forever?
Hmmm. Good question.
Off the top of my head, though, I don't think it matters. For now,
each of those macros (I presume) passes the context through the
dispatch table to the called function. So, if we change the interface
of a krb5_cc_* (for example), we will have to update every cc type's
corresponding function to know about it. As for the macro itself, the
header files can arrange for it to be correct (we may add another
argument, for example) based on the USE_KRB5_API_VERSION symbol. At
some point in the future, we may want to convert them to real
functions, but I don't think api versioning will have anything to do
with the decision.
Barry
