From: "Marcos P" <mparedesx@gmail.com>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Fwd: Help with l2cap broadcast programming
Date: Tue, 25 Apr 2006 00:14:43 +0100 [thread overview]
Message-ID: <55cd79280604241614m5da5e078s6374f8218d834656@mail.gmail.com> (raw)
In-Reply-To: <444D0164.5000505@xmission.com>
[-- Attachment #1: Type: text/plain, Size: 1713 bytes --]
Thank you Brad, for your answer. I am not using AVDTP, we have our own
algorithm to deliver video. The video stream is sent by modifying the
packetization and delivery scheme. For example sending 1 video slice per
packet and delivering each packet with times closer to a Real time
streamming. In this case the broadcast scheme in the bluetooth standard [*]
seems like a good way to stream video to different clients. In this case the
clients performance will be observed at different distances, and because
they are only in a listening state and the broadcast delivery is not
dependant to the buffer in the client; it is a good case study to analyse
the degradation of service at different positions.
at this time, I was starting to analyse how to use raw sockets in HCI and
l2cap to see if I was able to activate the broadcast mode, however if the
broadcast support is not in the bluez stack shall I then move to the AFFIX
stack???
It is really a pity that the bluez lacks the support for broadcast. I
kindly like the TCP/IP sockets similarity of socket programming with bluez.
Regards Marcos
*
http://www.bluetooth.com/Bluetooth/Learn/Works/Data_Transport_Architecture.htm
On 4/24/06, Brad Midgley <bmidgley@xmission.com> wrote:
>
> Hey
>
> >>The core spec talks about broadcast... lt_addr is all 0, llid = 10, ptt
> >>= 0. I looked around for examples using bluez but couldn't find any.
>
> If bluez really can't do this now, you can get it using the affix stack.
> We just can't discuss affix here unless it's in the context of improving
> bluez.
>
> (There's a special place in hell reserved for replying to myself twice
> here :)
>
> Brad
>
>
[-- Attachment #2: Type: text/html, Size: 2820 bytes --]
prev parent reply other threads:[~2006-04-24 23:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-24 0:28 [Bluez-devel] Help with l2cap broadcast programming Marcos P
2006-04-24 11:16 ` Fwd: " Marcos P
2006-04-24 15:58 ` [Bluez-devel] " Brad Midgley
2006-04-24 16:14 ` Brad Midgley
2006-04-24 16:48 ` Brad Midgley
2006-04-24 23:14 ` Marcos P [this message]
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=55cd79280604241614m5da5e078s6374f8218d834656@mail.gmail.com \
--to=mparedesx@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