Return-Path: Message-ID: From: "Albert Huang" To: bluez-devel@lists.sourceforge.net Subject: Re: [Bluez-devel] How to process fragmentation synchronously when two l2cap connections over one acl connection? In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_8958_4095664.1144946954028" References: <9FBCE015AF479F46B3B410499F3AE05B011F0BCB@pdsmsx405> 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 12:49:14 -0400 ------=_Part_8958_4095664.1144946954028 Content-Type: text/plain; charset=ISO-2022-JP Content-Transfer-Encoding: 7bit Content-Disposition: inline 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. -albert On 4/13/06, gao.yingbin@zte.com.cn wrote: > > > Marcel & all, > I'am puzzling over the following question. How to process fragmentation > synchronously when two l2cap connections over one acl connection? > in bluetooth specification, the continuing fragments of l2cap only can be > identified by acl connection handles. so if two l2cap connections build over > one acl conncetion (such as two l2cap connections bulid between two > bluetooth devices), and the two l2cap connections received continuing > fragments synchronously，how can i identify which fragments belong the first > l2caps connections and which fragments belong the other? > thanks. > > > > -------------------------------------------------------- > ZTE Information Security Notice: The information contained in this mail is solely property of the sender's organization. This mail communication is confidential. Recipients named above are obligated to maintain secrecy and are not permitted to disclose the contents of this communication to others. > This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the originator of the message. Any views expressed in this message are those of the individual sender. > This message has been scanned for viruses and Spam by ZTE Anti-Spam system. > > ------=_Part_8958_4095664.1144946954028 Content-Type: text/html; charset=ISO-2022-JP Content-Transfer-Encoding: 7bit Content-Disposition: inline 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.

-albert

On 4/13/06, gao.yingbin@zte.com.cn <gao.yingbin@zte.com.cn > wrote:

Marcel & all,
  I'am puzzling over the following question. How to process fragmentation synchronously when two l2cap connections over one acl connection?
 in bluetooth specification, the continuing fragments of l2cap only can be identified by acl connection handles. so if two l2cap connections build over one acl conncetion (such as two l2cap connections bulid  between two bluetooth devices), and the two l2cap connections received continuing fragments synchronously，how can i identify which fragments belong the first l2caps connections and which fragments  belong the other?
thanks. 



--------------------------------------------------------
ZTE Information Security Notice: The information contained in this mail is solely property of the sender's organization. This mail communication is confidential. Recipients named above are obligated to maintain secrecy and are not permitted to disclose the contents of this communication to others.

This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the originator of the message. Any views expressed in this message are those of the individual sender.

This message has been scanned for viruses and Spam by ZTE Anti-Spam system.

------=_Part_8958_4095664.1144946954028-- ------------------------------------------------------- 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