Hi, On Thu, Jun 16, 2011 at 2:33 PM, Andrzej Kaczmarek <andrzej.kaczmarek@xxxxxxxxx> wrote: > Why do you think re-creating the socket is not going to work? How it is > different than second attempt to connect SCO when eSCO failed, which is now > handled inside kernel? The same could be done by user-space but in more > sophisticated way which suits specific requirements. And this is how > negotiation is solved. Well the socket API is not meant to do this type of negotiation while connecting, you basically have connect/accept and in case you fail to configure you have to give up this socket and create a new one, also the error reported by the socket may not be enough to you to figure out what went wrong the first time to retry. > And what qualification testing will it break? > > > Could you please elaborate a little bit more on the above questions so I can > understand your point of view better. > > BR, > Andrzej > -- > To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" > in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html > -- Luiz Augusto von Dentz -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
