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

Marcel Holtmann
2006-08-20T03:15:37Z

Hi Matthew,

> > 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 think a lot of people missed the discussions behind the API since we
did them basically behind closed doors. The main focus will always be
the client application. You really have to think the other way around.

> > 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 the weird indentifiers are free formed strings that doesn't match
any of the other categories. And since the server will hand them out it
is an easy requirement to fulfill. These are also not meant to have any
meaning. In general they can be random garbage. The server knows what to
do with them.

You will also see that we love using strings, because in languages like
Python they are so easy to handle. If it is not an integer by definition
we might go with a string as type, because it is more flexible.

Regards

Marcel