public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: "Nick Pelly" <npelly@google.com>
To: "BlueZ development" <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] A2DP over DBUS
Date: Tue, 16 Sep 2008 09:56:00 -0700	[thread overview]
Message-ID: <35c90d960809160956g186fc668p7970c4f6a4d4bf70@mail.gmail.com> (raw)
In-Reply-To: <f21e7dc80809131154s7d0b7e99t23201743f65e1f50@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 2235 bytes --]

On Sat, Sep 13, 2008 at 11:54 AM, Choi Sonim <choisonim@gmail.com> wrote:

> Hi Marcel,
>
> On Sat, Sep 13, 2008 at 9:47 PM, Marcel Holtmann <marcel@holtmann.org>
> wrote:
> >> 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) ?


Android is definitely not pure Java, although third party apps for Android
are recommended to use the Java API's.

The built in Android profiles currently open sockets with the kernel in C
code.

Can they connect directly to those sockets
> from Java applications ?


In Android v1.0 we will not have stable Java API's to use Bluetooth :(

In the near future we intend to expose RFCOMM, L2CAP and SCO (control only)
via a Java Socket-like API for third party app development.


> Thank you a lot
> Choi
>
> >
> > 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
> >
>
> -------------------------------------------------------------------------
> 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
>

[-- Attachment #1.2: Type: text/html, Size: 3665 bytes --]

[-- Attachment #2: Type: text/plain, Size: 363 bytes --]

-------------------------------------------------------------------------
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=/

[-- Attachment #3: Type: text/plain, Size: 164 bytes --]

_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

      parent reply	other threads:[~2008-09-16 16:56 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
2008-09-16 16:56         ` Nick Pelly [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=35c90d960809160956g186fc668p7970c4f6a4d4bf70@mail.gmail.com \
    --to=npelly@google.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