Followup-To: ASN.1 -> C API (was ASN.1 tools information)
Keywords: API
Sender: news@nmpd.oz.au
Nntp-Posting-Host: cassius
Reply-To: cmoore@nmpd.oz.au
Organization: Telecom Australia.
Date: Wed, 22 Jul 1992 02:16:57 GMT
Lines: 26
While looking at a set of requirements for generalised binding between ASN.1 and "C" could prove to be usefull, my suggestion is to learn from what experience (if any) has been gained from current ASN.1 to "C" bindings.
Having been through this process, and also reviewing the proposed X/Open XOM and XMP API specifications (these seem to be gaining support) I am concerned that there has not been any significant practical use of these API (at least for OSI product parts), a clear example is the way the "user managed associations" has been specified (or what is missing from the specification), in addition the way (mandatory) synchronous operations have been specified also is a concern for implementors and their application
users.
Having stated the above, I would be interested in exchanging views on the X/Open API's with developers of OSI related products.