Re: Call for volunteers for C/C++ API liaison manager

Ted Lemon <ted.lemon@nominum.com> Fri, 02 May 2014 12:53 UTC

Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6A2101A6F84 for <ietf@ietfa.amsl.com>; Fri, 2 May 2014 05:53:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.551
X-Spam-Level:
X-Spam-Status: No, score=-2.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.651] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nJSsH75kKF4z for <ietf@ietfa.amsl.com>; Fri, 2 May 2014 05:53:12 -0700 (PDT)
Received: from shell-too.nominum.com (shell-too.nominum.com [64.89.228.229]) by ietfa.amsl.com (Postfix) with ESMTP id 8AFBD1A6F54 for <ietf@ietf.org>; Fri, 2 May 2014 05:53:12 -0700 (PDT)
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 877581B81EB for <ietf@ietf.org>; Fri, 2 May 2014 05:53:10 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id 6AE6819005C; Fri, 2 May 2014 05:53:10 -0700 (PDT)
Received: from [10.0.10.40] (192.168.1.10) by CAS-01.WIN.NOMINUM.COM (192.168.1.100) with Microsoft SMTP Server (TLS) id 14.3.158.1; Fri, 2 May 2014 05:53:10 -0700
Content-Type: text/plain; charset="windows-1252"
MIME-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
Subject: Re: Call for volunteers for C/C++ API liaison manager
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <20140502073200.GA5957@nic.fr>
Date: Fri, 2 May 2014 08:52:59 -0400
Content-Transfer-Encoding: quoted-printable
Message-ID: <D66D22A0-F9FC-4F3D-9747-1410AF454FB7@nominum.com>
References: <EB423B81-41F2-480D-B1EE-80E1753E1CDB@iab.org> <53618BDD.1080900@isi.edu> <5361B341.4000200@gmail.com> <5361B9FF.4020107@isdg.net> <20140502073200.GA5957@nic.fr>
To: Stephane Bortzmeyer <bortzmeyer@nic.fr>
X-Mailer: Apple Mail (2.1874)
X-Originating-IP: [192.168.1.10]
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/VxwF5c-ohOUatJ3NADrXoDK_xd0
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 May 2014 12:53:13 -0000

On May 2, 2014, at 3:32 AM, Stephane Bortzmeyer <bortzmeyer@nic.fr> wrote:
> In my experience, so called "high-level" API are not high-level at
> all, they always assume a specific programming style, typically the
> one of the language the author prefers.

The point is not to describe in detail the entry points to an API, but rather to describe the minimum functionality that an API should provide in order to allow the language and programs written in it to fully exploit the protocol.   In MIF we talk about the low-level API and the high-level API; the low-level API is just a list of functions the API has to provide; the high-level API is built on that, and is likely language-specific.   You can't build the language-specific API from just the abstract low-level API—you need to understand the locking/threading behavior of your language, and the memory allocation strategy, and so on.