[17435] in Kerberos_V5_Development
Re: Future ASN.1 support
daemon@ATHENA.MIT.EDU (Greg Hudson)
Fri Dec 9 16:09:05 2011
Message-ID: <4EE25E63.7050706@mit.edu>
Date: Fri, 09 Dec 2011 14:15:47 -0500
From: Greg Hudson <ghudson@mit.edu>
MIME-Version: 1.0
To: Nathaniel McCallum <npmccallum@redhat.com>
In-Reply-To: <1323457433.25965.35.camel@localhost>
Cc: krbdev@mit.edu
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: krbdev-bounces@mit.edu
On 12/09/2011 02:03 PM, Nathaniel McCallum wrote:
> 1. asn1c + using asn1c's types directly represents in my mind roughly
> equivalent work as writing your own compiler. I think the end result is
> better since it offloads completely a task from krb5 and completely
> eliminates the need to write conversion shims for new data types. The
> only downside that I can see is that it will break API/ABI. Why not just
> bite the bullet and call it 2.0?
This is not an option on the table. We are not prepared to break API
and ABI compatibility, and certainly not just for the sake of easier
ASN.1 encoding and decoding. Moreover, wedding our API and ABI to the
output of particular ASN.1 tool is not an attractive option.
_______________________________________________
krbdev mailing list krbdev@mit.edu
https://mailman.mit.edu/mailman/listinfo/krbdev
