From: Mike Lee <eemike@gmail.com>
To: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] About rfcomm
Date: Sun, 5 Dec 2004 05:10:45 -0800 [thread overview]
Message-ID: <1ffb4b0704120505108a498f3@mail.gmail.com> (raw)
Dear all
Could anyone tell me , Could i use datagram socket for rfcomm? if
not, Which layer should i use on application like e.g. video streaming
. l2cap? Or anyone do such a thing before?
best regard
Mike,Lee
--
-------------------------------------------------------
Mike Lee
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next reply other threads:[~2004-12-05 13:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-05 13:10 Mike Lee [this message]
2004-12-05 13:23 ` [Bluez-devel] About rfcomm 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=1ffb4b0704120505108a498f3@mail.gmail.com \
--to=eemike@gmail.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