From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Subject: Re: [Bluez-devel] How to process fragmentation synchronously when two l2cap connections over one acl connection? From: Marcel Holtmann To: bluez-devel@lists.sourceforge.net In-Reply-To: References: <9FBCE015AF479F46B3B410499F3AE05B011F0BCB@pdsmsx405> Content-Type: text/plain Message-Id: <1144948700.11159.53.camel@localhost> Mime-Version: 1.0 Sender: bluez-devel-admin@lists.sourceforge.net Errors-To: bluez-devel-admin@lists.sourceforge.net Reply-To: bluez-devel@lists.sourceforge.net List-Unsubscribe: , List-Id: BlueZ development List-Post: List-Help: List-Subscribe: , List-Archive: Date: Thu, 13 Apr 2006 19:18:20 +0200 Hi Albert, > l2cap packets are always identified by a channel ID, which is > negotiated when each l2cap connection (channel) is established. > Continuation fragments always have the channel ID in the packet > header, so there is no ambiguity over which continuation fragment > belongs to which connection. You should take another look at the > L2CAP section in the core spec. you are not allowed to mix L2CAP fragments. As simple as that. Regards Marcel ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ Bluez-devel mailing list Bluez-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bluez-devel