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 19:56:38 +0200 [thread overview]
Message-ID: <1188582998.13373.102.camel@violet> (raw)
In-Reply-To: <cc1649d10708310723h5eff2001sd95a186888e8dc03@mail.gmail.com>
Hi Vlad,
> I was talking about native code libraries....
> Anyway:
> The question is is it possible to open and accept RFCOMM and L2CAP
> connections just using D-Bus?
that is a question for your lawyers actually. I tend to say that once
you incluce l2cap.h or rfcomm.h you include GPL code thus your code
becomes GPL, too.
The serial port service however allows you to create RFCOMM connections
and then map them to a serial port on your system. That can be used from
D-Bus. For L2CAP such thing makes no sense.
For OBEX connection at some point the obex-data-server will provide a
D-Bus interface for it.
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
next prev parent reply other threads:[~2007-08-31 17:56 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
2007-08-31 14:23 ` Vlad Skarzhevskyy
2007-08-31 17:56 ` Marcel Holtmann [this message]
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=1188582998.13373.102.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox