From: Marcel Holtmann <marcel@holtmann.org>
To: Michel Planques <mplanque@laas.fr>
Cc: kdesai@mail.smu.edu,
BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] L2CAP connectionless
Date: Tue, 17 Feb 2004 00:00:04 +0100 [thread overview]
Message-ID: <1076972404.2840.60.camel@pegasus> (raw)
In-Reply-To: <3902.82.255.26.193.1076967794.squirrel@www.laas.fr>
Hi Michel,
> As I know, a L2CAP link is connection oriented, so I don't understand how
> the connectionless mode is working.
it supports both, but the most used is the connection oriented.
> I already searched informations about SOCK_DGRAM implementation in Bluez
> and never found anything : even in this mailing list (maybe I'm blind !)
> If anybody could point me on some informations ...
Some time ago Max includes support for SOCK_DGRAM and there was a
discussion about it, but I wasn't involved in it.
Regards
Marcel
-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2004-02-16 23:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-16 8:34 [Bluez-users] L2CAP connectionless Desai, Keyur Rajnikant
2004-02-16 9:01 ` Marcel Holtmann
2004-02-16 21:43 ` Michel Planques
2004-02-16 23:00 ` Marcel Holtmann [this message]
2004-02-17 15:47 ` [Bluez-users] Mailing list gateway corrupting messages (was: L2CAP connectionless) Steven Singer
2004-02-17 16:56 ` Marcel Holtmann
-- strict thread matches above, loose matches on Subject: below --
2004-02-16 22:20 [Bluez-users] L2CAP connectionless Desai, Keyur Rajnikant
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=1076972404.2840.60.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-users@lists.sourceforge.net \
--cc=kdesai@mail.smu.edu \
--cc=mplanque@laas.fr \
/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