All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] JSR-82 using D-Bus
Date: Fri, 31 Aug 2007 16:07:07 +0200	[thread overview]
Message-ID: <1188569227.13373.94.camel@violet> (raw)
In-Reply-To: <cc1649d10708301947o7fbb805dsfb2a7df83d39ec@mail.gmail.com>

Hi Vlad,

>   I'm developing BlueCove JSR-82. I have major windows stacks covered.
> Now I'm thinking about BlueZ.
> 
>   I have an idea to implement JSR-82 on top of BlueZ using just D-Bus
> API.  Do you think it is possible?
> 
>   The problem is that BlueCove is LGPL (not GPL)  so I can't really
> link BlueZ libraries.

the D-Bus API can be used with whatever license you want.

Regards

Marcel



-------------------------------------------------------------------------
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-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2007-08-31 14:07 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-31  2:47 [Bluez-users] JSR-82 using D-Bus Vlad Skarzhevskyy
2007-08-31 14:07 ` Marcel Holtmann [this message]
2007-08-31 14:23   ` Vlad Skarzhevskyy
2007-08-31 17:56     ` Marcel Holtmann
2007-08-31 20:45       ` Vlad Skarzhevskyy
2007-08-31 21:01         ` Marcel Holtmann
2007-09-01  3:14           ` Vlad Skarzhevskyy
2007-09-01  3:26             ` Manuel Naranjo
2007-09-01  5:14               ` Vlad Skarzhevskyy

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=1188569227.13373.94.camel@violet \
    --to=marcel@holtmann.org \
    --cc=bluez-users@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.