RE: [Bluez-devel] Qualification Testing

["Daryl Van Vorst" <daryl@wideray.com>]

Max,

> >Having the messages appear on the console is enough to pass=20
> testing. We=20
> >shouldn't need a special app that monitors syslog. We could submit a=20
> >copy of the syslog if necessary.
> Hmm, ok :). But after thinking more about this I think that=20
> we probably still need=20
> some way to tell the apps that link became unreliable. I mean=20
> parsing syslogs is=20
> not very elegant solution :). Also even though Cetecom=20
> accepted it as a solution=20
> other BQBs might not.

Technically Cetecom hasn't accepted it yet. That's just preliminary. The BQ=
B
hasn't reviewed the data.

> Here is what I had in mind. We could add L2CAP socket option=20
> L2CAP_RELIABILITY, which will be used by the apps that are=20
> "paranoid" :) about link reliability. Then whenever we=20
> receive corrupted L2CAP frame we'd check connected sockets,=20
> attached to this connection, that have this option enabled=20
> and signal error condition on them.=20
> i.e. read/recvmsg will return error. Application can then=20
> either clear that error with=20
> getsockopt(SO_ERROR) and continue or close the socket.
>=20
> Comments ?

That sounds great to me! That's the sort of thing I was hoping for in the
beginning, but I knew too little about sockets to suggest a workable
solution. :)

-Daryl.