From: Erik Tews <erik@debian.franken.de>
To: Alexandros Karypidis <karypid@inf.uth.gr>
Cc: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] JSR-82 Implementation
Date: Mon, 16 Aug 2004 16:45:50 +0200 [thread overview]
Message-ID: <1092667550.3452.88.camel@localhost.localdomain> (raw)
In-Reply-To: <200408161547.34493.karypid@inf.uth.gr>
Am Mo, den 16.08.2004 schrieb Alexandros Karypidis um 14:47:
> You might also have a look at:
>
> https://sourceforge.net/projects/avetanabt/
>
> OBEX stuff is missing (we're working on wrapping around libopenobex) and
> will come around some time this fall.
>
> Also, keep in mind that is J2SE/BlueZ based. So if you're using some
> sort of J2ME implementation for Linux, it won't work, complaining about
> missing classes...
I am going to write a software where a j2me mobile phone (or a pda)
needs to talk to a server, which will be running linux and will be a
full featured pc. So I will got a j2se java on this system.
The Viewcvs on sourceforge is currently down and there is no homepage, I
will have a look at this project when it is back again?
I need no obex-stuff, just some rfcomm-channels.
-------------------------------------------------------
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2004-08-16 14:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-13 20:08 [Bluez-devel] JSR-82 Implementation Erik Tews
2004-08-16 10:02 ` Stephen Crane
2004-08-16 12:02 ` Erik Tews
2004-08-16 12:47 ` Alexandros Karypidis
2004-08-16 14:45 ` Erik Tews [this message]
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=1092667550.3452.88.camel@localhost.localdomain \
--to=erik@debian.franken.de \
--cc=bluez-devel@lists.sourceforge.net \
--cc=karypid@inf.uth.gr \
/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.