From: Marcel Holtmann <marcel@holtmann.org>
To: Julien Campana <juliencampana@yahoo.fr>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Announce : BlueZ-based implemantation of JSR82
Date: Tue, 25 May 2004 15:36:45 +0200 [thread overview]
Message-ID: <1085492205.9779.119.camel@pegasus> (raw)
In-Reply-To: <1085489942.900.89.camel@fischer>
Hi Julien,
> > 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.
it is not, because as you mention later that you have to copy or rewrite
some of the BlueZ functions to fulfil the need for JSR-82. We should
talk about that and see what we can fixup in BlueZ.
What I also don't wanna use is somekind of "de.avetana.bluetooth" vendor
extensions. If something is not possible in pure Java JSR-82, sorry not
my bad ;)
And another important point for me is the coding style. The use of tabs
(8 spaces) is a must, because it makes the code easier to read and keep
developers from over-nesting.
> 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).
The native interface should only be a wrapper. Let's talk about the
stuff and put some of it back to the Bluetooth library where it should
belong.
> > 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.
I know Java and I did a lot of programming with Java in the past, but I
haven't done anything in the last 5 years. May you write a small howto
for getting your stuff run. For me preferable with Debian Sid.
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by: Oracle 10g
Get certified on the hottest thing ever to hit the market... Oracle 10g.
Take an Oracle 10g class now, and we'll give you the exam FREE.
http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2004-05-25 13:36 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
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 ` Marcel Holtmann [this message]
[not found] ` <1085496174.900.127.camel@fischer>
2004-05-25 15:07 ` [Bluez-devel] Announce : BlueZ-based implemantation of JSR82 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=1085492205.9779.119.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
--cc=juliencampana@yahoo.fr \
/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