From owner-freebsd-bluetooth@FreeBSD.ORG Fri Nov 7 22:32:51 2008 Return-Path: Delivered-To: freebsd-bluetooth@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3E37E1065673 for ; Fri, 7 Nov 2008 22:32:51 +0000 (UTC) (envelope-from plunky@rya-online.net) Received: from smtp01.one2one.net (smtp01.one2one.net [149.254.200.196]) by mx1.freebsd.org (Postfix) with ESMTP id F0B498FC19 for ; Fri, 7 Nov 2008 22:32:50 +0000 (UTC) (envelope-from plunky@rya-online.net) Received: from [127.0.0.1] (helo=localhost) by smtpbarns01 with esmtp (Exim 4.50) id 1KyZsn-0004Sf-El; Fri, 07 Nov 2008 22:32:49 +0000 Received: from smtpbarns01 ([127.0.0.1]) by localhost (smtpbarns01 [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 16871-08; Fri, 7 Nov 2008 22:32:49 +0000 (GMT) Received: from [10.199.59.87] (helo=rya-online.net) by smtpbarns01 with smtp (Exim 4.50) id 1KyZsl-0004Sa-Vw; Fri, 07 Nov 2008 22:32:49 +0000 Received: (nullmailer pid 698 invoked by uid 1000); Fri, 07 Nov 2008 22:31:39 -0000 Date: Fri, 7 Nov 2008 22:31:39 +0000 (GMT) To: Guido Falsi In-Reply-To: <4914B113.60303@madpilot.net> References: <20081104111947.GB62907@megatron.madpilot.net> <1225799105.807983.1164.nullmailer@galant.ukfsn.org> <20081104135107.GA64776@megatron.madpilot.net> <1225821264.107584.759.nullmailer@galant.ukfsn.org> <4910B6E6.7070206@madpilot.net> <4910CA97.6030708@madpilot.net> <1226091521.039371.399.nullmailer@galant.ukfsn.org> <4914B113.60303@madpilot.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Message-Id: <1226097099.328979.788.nullmailer@galant.ukfsn.org> From: Iain Hibbert X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at example.com X-SA-Exim-Connect-IP: 127.0.0.1 X-SA-Exim-Mail-From: plunky@rya-online.net X-SA-Exim-Scanned: No (on smtpbarns01); SAEximRunCond expanded to false Cc: freebsd-bluetooth@freebsd.org Subject: Re: RFComm behaviour with nokia mobiles 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: Fri, 07 Nov 2008 22:32:51 -0000 On Fri, 7 Nov 2008, Guido Falsi wrote: > Iain Hibbert wrote: > > The attribute ID list should be in ascending order according to the > > specification. This means though that some logic could be wrong because > > the protocol descriptor list for any given service class would likely > > appear before the service name in the response attribute list and you > > would use the wrong channel.. > > Uhm, I did not get this detail in the specification. You can find this in the small print of the SDP spec sections relating to ServiceSearch and ServiceSearchAttribute requests, in the AttributeIDList box. I guess its so that a server can do a straight pass through search without having to loop up and down the list, but I don't know if that would work out simpler or not in practice. Obviously the Nokia people thought not, as it worked anyway :) iain