Return-Path: Subject: RE: [Bluez-devel] Qualification Testing From: Marcel Holtmann To: Max Krasnyansky Cc: Daryl Van Vorst , "'BlueZ Mailing List'" In-Reply-To: <5.1.0.14.2.20030513095851.0d257510@unixmail.qualcomm.com> References: <000201c31771$70577930$6400a8c0@baked> <5.1.0.14.2.20030513095851.0d257510@unixmail.qualcomm.com> Content-Type: text/plain Message-Id: <1052865099.4608.9.camel@pegasus.local> Mime-Version: 1.0 Sender: bluez-devel-admin@lists.sourceforge.net Errors-To: bluez-devel-admin@lists.sourceforge.net List-Help: List-Post: List-Subscribe: , List-Id: List-Unsubscribe: , List-Archive: Date: 14 May 2003 00:31:32 +0200 Hi Max, > Hmm, ok :). But after thinking more about this I think that we probably still need > some way to tell the apps that link became unreliable. I mean parsing syslogs is > not very elegant solution :). Also even though Cetecom accepted it as a solution > other BQBs might not. > > Here is what I had in mind. We could add L2CAP socket option L2CAP_RELIABILITY, > which will be used by the apps that are "paranoid" :) about link reliability. > Then whenever we receive corrupted L2CAP frame we'd check connected sockets, attached > to this connection, that have this option enabled and signal error condition on them. > i.e. read/recvmsg will return error. Application can then either clear that error with > getsockopt(SO_ERROR) and continue or close the socket. the idea itself sounds very good. But I see no advantage in implementing such kind of extra functionality. We can not detect if a frame is currupt or not, because we have no checksum mechanism. The only thing we can detect is a length mismatch. What about a corrupted cid? If you notify the wrong socket and the application on that socket can't deal with such an error. Regards Marcel ------------------------------------------------------- Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara The only event dedicated to issues related to Linux enterprise solutions www.enterpriselinuxforum.com _______________________________________________ Bluez-devel mailing list Bluez-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bluez-devel