public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Rogue <roguexz@gmail.com>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Does BlueZ have java bindings?
Date: Tue, 07 Aug 2007 19:17:01 +0530	[thread overview]
Message-ID: <46B877D5.1050105@gmail.com> (raw)
In-Reply-To: <46B7FAFF.8080304@idlum.be>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


Pierre-Yves Paulus wrote:
> Hi Rogue,
> 
> Use the DBus API.
> http://bluez.cvs.sourceforge.net/bluez/utils/hcid/dbus-api.txt?view=markup
> 
> Java DBus bindings are available there:
> http://www.freedesktop.org/wiki/Software/DBusBindings
> 

Thanks Pierre,

I am looking into the Dbus bindings right now.

regards,
Rogue

> Best Regards,
> Pierre-Yves
> 
> Rogue wrote:
> Hi All,
> 
> Just checking, if the bluez stack has java bindings? If it does, how do
> I go about acquiring it?
> 
> thanks,
> Rogue

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)

iD8DBQFGuHfVceS9IQvx51YRAuT/AKCXU+1SOxwUbM2wpYBz0oAA1z5qaQCgwsrO
mFYd4j0ACqr/5UZVGrf/7gk=
=LO4e
-----END PGP SIGNATURE-----

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

      reply	other threads:[~2007-08-07 13:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-05 17:38 [Bluez-devel] Does BlueZ have java bindings? Rogue
2007-08-07  4:54 ` Pierre-Yves Paulus
2007-08-07 13:47   ` Rogue [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=46B877D5.1050105@gmail.com \
    --to=roguexz@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