From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] A2DP over DBUS
Date: Sat, 13 Sep 2008 21:54:42 +0200 [thread overview]
Message-ID: <1221335682.6695.60.camel@californication> (raw)
In-Reply-To: <f21e7dc80809131154s7d0b7e99t23201743f65e1f50@mail.gmail.com>
Hi Choi,
> >> Can you please explain briefly what's the underlying method that the
> >> plugin uses to send the data to bluez then ? does it directly uses
> >> sockets and sends it to the kernel ?
> >
> > direct SCO or L2CAP sockets to have a low latency and to avoid copying
> > data around.
>
> That's interesting. What about platforms like Android that are only
> Java (If I am not wrong) ? Can they connect directly to those sockets
> from Java applications ?
that is an issue of their applications. However if they integrate with
common Linux standards like ALSA, GStreamer etc. then it is hidden from
the actual audio application.
Regards
Marcel
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2008-09-13 19:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-13 17:26 [Bluez-devel] A2DP over DBUS Choi Sonim
2008-09-13 18:27 ` Marcel Holtmann
2008-09-13 18:32 ` Choi Sonim
2008-09-13 18:47 ` Marcel Holtmann
2008-09-13 18:54 ` Choi Sonim
2008-09-13 19:12 ` Brad Midgley
2008-09-13 19:54 ` Marcel Holtmann [this message]
2008-09-16 16:56 ` Nick Pelly
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=1221335682.6695.60.camel@californication \
--to=marcel@holtmann.org \
--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