Re: [Bluez-devel] [PATCH] implement RFCOMM Connect and Disconnect methods

Matthew Garrett
2006-08-20T00:31:54Z

On Sun, Aug 20, 2006 at 04:13:48AM +0200, Marcel Holtmann wrote:

> I meant exactly that. The method should work out what information got
> passed to it. Of course this might not be easy to implement, but that is
> not the point behind this API. The whole API is designed to make it easy
> for all kind of applications. And the main focus is not the C language.

Ok, cool. Now I know what to aim for, I'll head back to that :)

> I also don't see the problem here. The ASCII service string are a
> predefined list of names that actually match to specific UUID. Since in
> the end we will implement all needed service names for all known
> profiles, we only need to support UUID128. These have a unique form and
> are kinda easy to detect. If the provided UUID128 matches the Bluetooth
> base string, then we can internally use UUID32 or UUID16. As simple as
> that. For the record handles we give them in hex and so they are also
> easy to identify. And I would check the string in this order.

Ok, makes sense.

> And as said, this might require a little bit more code in hcid, but that
> is the price to pay if we wanna have a simple API for the application
> and I am paying it gladly.

Sure. I'll send a new patch tomorrow.