From owner-freebsd-bluetooth@FreeBSD.ORG Mon Dec 5 21:44:00 2005 Return-Path: X-Original-To: freebsd-bluetooth@freebsd.org Delivered-To: freebsd-bluetooth@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1169916A41F for ; Mon, 5 Dec 2005 21:44:00 +0000 (GMT) (envelope-from marcel@holtmann.org) Received: from mail.holtmann.net (coyote.holtmann.net [217.160.111.169]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4AC0543D5C for ; Mon, 5 Dec 2005 21:43:58 +0000 (GMT) (envelope-from marcel@holtmann.org) Received: from localhost.localdomain (localhost [127.0.0.1]) by mail.holtmann.net (8.13.4/8.13.4/Debian-3) with ESMTP id jB5LiGsF015161 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Mon, 5 Dec 2005 22:44:16 +0100 From: Marcel Holtmann To: Maksim Yevmenkin In-Reply-To: <43936F6B.1090003@savvis.net> References: <9307f5f20512030807x6eadc73cq9d9acc9dd5503a5b@mail.gmail.com> <4391E320.2090006@savvis.net> <9307f5f20512031333x61e9d141u85ea578711740712@mail.gmail.com> <43936F6B.1090003@savvis.net> Content-Type: text/plain Date: Mon, 05 Dec 2005 22:44:57 +0100 Message-Id: <1133819097.4559.15.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.5.2 Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DATE_IN_FUTURE_48_96 autolearn=failed version=3.0.3 X-Spam-Checker-Version: SpamAssassin 3.0.3 (2005-04-27) on coyote.holtmann.net X-Virus-Scanned: ClamAV 0.84/1204/Mon Dec 5 11:09:54 2005 on coyote.holtmann.net X-Virus-Status: Clean Cc: freebsd-bluetooth@freebsd.org Subject: Re: Automatic bluetooth device initialization X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Dec 2005 21:44:00 -0000 Hi Maksim, > while i appreciate your effort in this area, i'm skeptical that d-bus > and/or whatever api will solve this problem. i think, instead of > introducing yet another compatibility layer that sits on top of native > api, everyone would be much better off if native api was the same. what > would solve this problem, imo, is the standard (something like posix) > that would define api etc. I don't really like D-Bus, but it will be the way to go for a general API for the desktop. It has multiple language bindings already and our goal is to make it totally generic (no BlueZ specific definitions). Regards Marcel