Re: [Bluez-devel] l2cap and multiple connections

[Marcel Holtmann <marcel@holtmann.org>]

Hi Vlad,

> > you should step down to a book for socket programming. Which actually
> > means bind() once and accept() often ;)
> 
>   I know this is how it's normally done, but since
> I was using HCI before, and connections had to be initiated by the
> "master", I thought the method I mentioned was the way to use.
> 
>   So, from what your saying, I should listen() and accept() at the 
> bluetooth "master"? Is there an implicit role-change command
> happening somewhere, cause if I accept at the "master", otherwise,
> that would mean that the connection is initiated by the "slave", which
> is not as the bluetooth spec, right? How does it work?

the master is the device that creates the connection. That is what the
Bluetooth specification says. This means that an access point for
example is not a master per se, but it can tell a client to become
slave. Look at the L2CAP socket options for the master link policy.

> "eSCO"? Never heard about that. Thanks, I'll look into that.

It is part of the Bluetooth 1.2 specification.

Regards

Marcel




-------------------------------------------------------
This SF.Net email is sponsored by: SourceForge.net Broadband
Sign-up now for SourceForge Broadband and get the fastest
6.0/768 connection for only $19.95/mo for the first 3 months!
http://ads.osdn.com/?ad_id=2562&alloc_id=6184&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel