Date: Sat, 08 Nov 2008 13:20:45 +0100 From: Guido Falsi <mad@madpilot.net> To: Iain Hibbert <plunky@rya-online.net> Cc: freebsd-bluetooth@freebsd.org Subject: Re: RFComm behaviour with nokia mobiles Message-ID: <4915841D.1060503@madpilot.net> In-Reply-To: <1226135769.665964.502.nullmailer@galant.ukfsn.org> 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> <1226097099.328979.788.nullmailer@galant.ukfsn.org> <4914E54B.4060206@madpilot.net> <1226135769.665964.502.nullmailer@galant.ukfsn.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Iain Hibbert wrote: >> I think FreeBSD's sdp is making 2 requests in this case...Or maybe forcing the >> order to be the same as the request. > > No, it does use a single ServiceSearchAttribute but I think its just that > the Nokia server iterates over the AttributeIDList with a pass through the > server record each time for attributes that match: > Now I understand it. An old sony ericcson T610 is acting the same as the 2 nokias I tried. Anyway to be on the safe side, as I said, i defined the request list in ascending order and expect answers in ascending order. > One thing that the current library code does not provide for is that the > ServiceSearchAttribute response is parsed into the sdp_attr_t array but > the caller has no way to know which record each attribute came from, so > that can cause problems when more than one record is matched. You might > also want to consider the case where a Serial Port service is matched that > does not have a Service Name field. Do you match it or ignore it? > original gnokii code is ignoring services without a name, so I'm ignoring them. I don't know exactly the chance of such a situation., Keep in mind that gnokii is interested in talking just to mobile phones, not to any kind of bluetooth device, so the function does not have any need to be too generic. > > PPS wtf is "m-Router connectivity" anyway? I don't have the slightest idea :P Mobile phones come with a lot of strange services... Googleing a little it looks like some kind of routing service used by nokia PC suite to share more services on just one logical connection. -- Guido Falsi <mad@madpilot.net>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4915841D.1060503>