From: "Vlad Skarzhevskyy" <skarzhevskyy@gmail.com>
To: "BlueZ users" <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] JSR-82 using D-Bus
Date: Fri, 31 Aug 2007 23:14:37 -0400 [thread overview]
Message-ID: <cc1649d10708312014s4ff62bd3o603905ab4d8dd221@mail.gmail.com> (raw)
In-Reply-To: <1188594085.10148.8.camel@violet>
Hi Marcel
My goal is to make open source JSR-82 and certify it with Motorola.
I can't do this with windows corporates. They will not make a minimal
modifications in the core to make it possible to make JSR-82 complaint
(100%) implementation on top...
> not sure that this will make you GPL compliant. Once you link it
> together the whole software becomes GPL.
This is fine. As long as as original BlueCove library exists in LGPL version.
> No idea. Never checked their source code. While I am open for
> suggestion's to support JSR-82 the best, I don't care that much because
> I am not a big Java fan.
Does this mean you will help me with advise while I'm doing JSR-82
on top of BlueZ?
I'm big fun of java :) and I can write in C/C++. As it is right now
I managed to create nearly compliant implementation on windows. There
are some missing parts that I can't fix in WIDCOMM to certify
implementation with Motorola. Also I'm hoping to make a version for
Toshiba stack. The API they have looks very promising. But this after
BlueZ.
I just started with BlueZ and managed to create device discovery
using D-Bus java binding. As I see there are many places where the are
missing documentation in BlueZ or unimplemented functionality e.g
Service framework does not give me ability to register L2CAP service.
Also if I want to register RFCOMM service but don't want map it to com
port and just handle it using sockets (not via D-Bus).....
So now I'm going for one week to the cottage. When back I will start
making noise in this group again.
--
Vlad
-------------------------------------------------------------------------
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-09-01 3:14 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
2007-08-31 20:45 ` Vlad Skarzhevskyy
2007-08-31 21:01 ` Marcel Holtmann
2007-09-01 3:14 ` Vlad Skarzhevskyy [this message]
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=cc1649d10708312014s4ff62bd3o603905ab4d8dd221@mail.gmail.com \
--to=skarzhevskyy@gmail.com \
--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