Re: KITTEN: IETF 75 - 76

Volker Lendecke <Volker.Lendecke@SerNet.DE> Thu, 03 September 2009 20:10 UTC

Return-Path: <Volker.Lendecke@SerNet.DE>
X-Original-To: kitten@core3.amsl.com
Delivered-To: kitten@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 356CD3A67FB for <kitten@core3.amsl.com>; Thu, 3 Sep 2009 13:10:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.249
X-Spam-Level:
X-Spam-Status: No, score=-6.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id D4mt6Djmi8MK for <kitten@core3.amsl.com>; Thu, 3 Sep 2009 13:10:01 -0700 (PDT)
Received: from mail.SerNet.de (mail1.SerNet.de [193.175.80.2]) by core3.amsl.com (Postfix) with ESMTP id 30F923A67C2 for <kitten@ietf.org>; Thu, 3 Sep 2009 13:10:00 -0700 (PDT)
Received: from intern.SerNet.DE by mail.SerNet.DE with esmtp (Exim 4.63 #1) id 1MjESq-0001XY-Al; Thu, 03 Sep 2009 17:43:08 +0200
Received: by intern.SerNet.DE id 1MjESp-003YOF-Vu; Thu, 03 Sep 2009 17:43:08 +0200
Received: by intern.SerNet.DE id 1MjESp-003YNh-P9; Thu, 03 Sep 2009 17:43:07 +0200
Date: Thu, 03 Sep 2009 17:43:11 +0200
From: Volker Lendecke <Volker.Lendecke@SerNet.DE>
To: Jeffrey Hutzelman <jhutz@cmu.edu>
Subject: Re: KITTEN: IETF 75 - 76
References: <396484EF-9812-40CE-9221-F1A1319FD10B@kth.se> <20090901181307.fe1d4efa.miallen@ioplex.com> <98F14484-1B48-45A1-86E7-5E78383F5109@kth.se> <20090901214059.17a309e6.miallen@ioplex.com> <4A9E22D9.9050405@samba.org> <20090902153241.GJ1033@Sun.COM> <20090902172015.da056c19.miallen@ioplex.com> <20090902212652.GX1033@Sun.COM> <395_1251953035_n834hs6R012125_20090902211200.8a2dd378.miallen@ioplex.com> <0AB8FDC38BE7B55EB358D7FA@minbar.fac.cs.cmu.edu>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="bg08WKrSYDhXBjb5"
Content-Disposition: inline
In-Reply-To: <0AB8FDC38BE7B55EB358D7FA@minbar.fac.cs.cmu.edu>
User-Agent: Mutt/1.5.18 (2008-05-17)
Message-Id: <E1MjESp-003YOF-Vu@intern.SerNet.DE>
Organization: SerNet GmbH, Goettingen, Germany
X-Mailman-Approved-At: Thu, 03 Sep 2009 21:45:32 -0700
Cc: kitten@ietf.org, Love@core3.amsl.com, Volker Lendecke <vl@SerNet.DE>, Nicolas Williams <Nicolas.Williams@sun.com>
X-BeenThere: kitten@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Volker.Lendecke@SerNet.DE
List-Id: Common Authentication Technologies - Next Generation <kitten.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/kitten>, <mailto:kitten-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/kitten>
List-Post: <mailto:kitten@ietf.org>
List-Help: <mailto:kitten-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/kitten>, <mailto:kitten-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Sep 2009 21:37:37 -0000

On Thu, Sep 03, 2009 at 10:45:01AM -0400, Jeffrey Hutzelman wrote:
> 1) Assume POSIX threads(*).
> 2) Assume POSIX threads(*), but allow the existence of an implementation
>   dependent means of indicating use of some other threading model.
> 3) Recognize that there is no sane way to provide an portable async API
>   without either a portable threading model or a portable event model,
>   and give up.  Applications which want to call the GSS-API in an
>   asynchronous manner can simulate it by running the GSS-API call in
>   its own thread (under a platform-specific thread model).

Sorry to step in here, but there's tons of example for
portable async APIs. One that I just adapted Samba to is the
API used in the avahi libs. You hand the avahi libs a set of
callback functions like "listen on this fd for read" and so
on, and you are called back by avahi when something
interesting happens.

This is definitely doable without the requirement for
threads. It may be a complex API, but async programming
never has been easy.

Volker