[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [bluetooth-dev] Auto_Accept_Flag



True, we haven't tested the autoaccept flag. Feel free to 
drop a patch for it.
brgds
Mattias

> -----Original Message-----
> From: fabrizio.gennari@xxxxxxx.com 
> [mailto:fabrizio.gennari@xxxxxxx.com]
> Sent: den 28 maj 2001 15:48
> To: bluetooth-dev@xxxxxxx.com
> Subject: [bluetooth-dev] Auto_Accept_Flag
> 
> 
> In the BT specs (part H:1, chapter 4.7.3) an Auto_Accept_Flag 
> is defined: when it is 1, a device receiving a connection 
> request automatically sends a positive response, WITHOUT 
> issuing a CONNECTION_REQUEST event to the upper layers. When 
> the connection 
> is complete, the CONNECTION_COMPLETE event happens. Axis 
> stack cannot handle this situation: if the 
> CONNECTION_COMPLETE event arrives, it looks for an L2CAP 
> connection, and if the CONNECTION_REQUEST hadn't arrived, the 
> L2CAP connection does not exist, so 
> the connection process stops.
> 
> Maybe the stack should not assume that the CONNECTION_REQUEST 
> event always happens: if an L2CAP connection does not exist 
> when CONNECTION_COMPLETE arrives, it should be created.
> ---------------------------------------------------------
> Fabrizio Gennari          tel. +39 039 203 7816
> Philips Research Monza    fax. +39 039 203 7800
> via G. Casati 23          fabrizio.gennari@xxxxxxx.com
> 20052 Monza (MI) Italy    http://www.research.philips.com
> -
> To unsubscribe from this list: send the line "unsubscribe 
> bluetooth-dev" in
> the body of a message to majordomo@xxxxxxx.com
> 
-
To unsubscribe from this list: send the line "unsubscribe bluetooth-dev" in
the body of a message to majordomo@xxxxxxx.com