From: Julien Campana <juliencampana@yahoo.fr>
To: Marcel Holtmann <marcel@holtmann.org>,
BlueZ-devel List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Announce : BlueZ-based implemantation of JSR82
Date: Tue, 25 May 2004 14:59:02 +0200 [thread overview]
Message-ID: <1085489942.900.89.camel@fischer> (raw)
In-Reply-To: <1085487245.9779.89.camel@pegasus>
Am Di, den 25.05.2004 schrieb Marcel Holtmann um 14:14:
> Hi Julien,
>
> > We have developped a JSR-82 implementation for Linux, which is based on
> > BlueZ and which is compatible with most USB-Dongle's.
> >
> > We've used parts of JavaBluetooth.org's works and parts of JBluez's
> > stuff.
> > The native C-Code of the project is entirely based on the BlueZ project
> > and I would like to thanks Marcel Holtmann for his answers to my
> > questions, which were all helpfull.
>
> you are welcome.
>
> > We've decided to make the Linux version OpenSource.
> >
> > The JSR-82 specification is not yet fully implemented but the major part
> > of the work (let say 95%) is done.
>
> I would never use Java for Bluetooth programming, but it seems that some
> companies wants this, especially mobile phone manufacturers. So I think
> we should build up a clean implementation of the JSR-82 standard that
> uses BlueZ as underlying Bluetooth stack.
This is exactly what I did, or at least I have implemented a big part of
the JSR-82 Standard with BlueZ as underlying Bluetooth stack. (I suppose
but do not really know if the implementation is clean:)). If you want
this implementation to be part of the BlueZ project, I (and especially
my boss:) agree.
> Clean means for me that we
> should concentrate on BlueZ and try to interface BlueZ<->JSR-82 as best
> as possible.
To better understand the way I have interfaced BlueZ <->JSR-82 and if
you have enough time for this, I invite you to have a quick look at the
file sources/c/BlueZ.cpp contained in the tgz archive downloadable at
http://www.avetana-gmbh.de/avetana-gmbh/jsr82.xml
This c file mostly re-write some BlueZ method and has surely to be
cleaned and documented.
This will be the next step of my work. This version is still a
beta-version but is stable and robust enough to be used in a project.
especially if the project uses RFCOMM connections. (there is still some
work to do with L2CAP).
> Give me some comments if there is really interest in doing
> this.
I will continue to work on this project until I reach a clean and really
stable implementation. If you have any comment about the implementation
do not hesitate to mail me.
Regards,
Julien
> Regards
>
> Marcel
>
next prev parent reply other threads:[~2004-05-25 12:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-24 10:07 [Bluez-devel] Announce : BlueZ-based implemantation of JSR82 Julien Campana
2004-05-24 10:55 ` Mauro Tortonesi
2004-05-25 12:14 ` Marcel Holtmann
2004-05-25 12:59 ` Julien Campana [this message]
2004-05-25 13:32 ` [Bluez-devel] Flush timeout at Baseband Wang Haiguang
2004-05-25 13:42 ` Marcel Holtmann
2004-05-25 13:36 ` [Bluez-devel] Announce : BlueZ-based implemantation of JSR82 Marcel Holtmann
[not found] ` <1085496174.900.127.camel@fischer>
2004-05-25 15:07 ` Marcel Holtmann
2004-05-27 10:21 ` Julien Campana
2004-05-27 10:45 ` Stephen Crane
2004-05-27 12:33 ` Marcel Holtmann
2004-05-27 12:28 ` Marcel Holtmann
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=1085489942.900.89.camel@fischer \
--to=juliencampana@yahoo.fr \
--cc=bluez-devel@lists.sourceforge.net \
--cc=marcel@holtmann.org \
/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.