public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: "Esther Lopez" <esther.lopez@erzia.com>
To: <bluez-devel@lists.sourceforge.net>
Subject: [Bluez-devel] L2CAP sockets
Date: Fri, 26 Aug 2005 13:19:33 +0200	[thread overview]
Message-ID: <20050826111844.1ACEC1DC1D6@mrelay2.st2.lyceu.net> (raw)

[-- Attachment #1: Type: text/plain, Size: 487 bytes --]

Hello you all!

 

I have a question related with BlueZ L2CAP sockets, and I hope somebody can
help me.

 

If I want to communicate two Bluetooth devices using L2CAP, I just open an
L2CAP socket and send data through this open socket. (Is this OK?). 

The question is related with the size and format of the data send throught
this socket. How is the data packet created? Do I need to create headers and
so on? What is the size of the data I can send?

 

Thanks in advance

 

Esther


[-- Attachment #2: Type: text/html, Size: 3047 bytes --]

             reply	other threads:[~2005-08-26 11:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-26 11:19 Esther Lopez [this message]
2005-08-26 11:32 ` [Bluez-devel] L2CAP sockets Marcel Holtmann

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20050826111844.1ACEC1DC1D6@mrelay2.st2.lyceu.net \
    --to=esther.lopez@erzia.com \
    --cc=bluez-devel@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox