linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Crane <jscrane@maths.tcd.ie>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Developing a basic service for BlueTooth enabled devices
Date: Wed, 11 Jan 2006 19:10:21 +0000	[thread overview]
Message-ID: <1137006621.7489.20.camel@localhost.localdomain> (raw)
In-Reply-To: <1136989762.3825.29.camel@localhost.localdomain>

[-- Attachment #1: Type: text/plain, Size: 1139 bytes --]

Hello world,

On Wed, 2006-01-11 at 15:29 +0100, Marcel Holtmann wrote:
> > My first approach was to develep a web service with Apache for WAP
> > enabled  browsers that would run locally on each Linux server boxes
> > and serve WAP pages to the local ad-hoc mobile clients in order to
> > eliminate the client side development effort. However, it looks like
> > for many mobile devices I won't be able to do that. I have Motorola
> > RAZR V3 Java enabled phone at home and I could not do this by
> > establishing a piconet between my Kubuntu box and RAZR V3. 
> > 
> > What would be your suggestion? What kind of client/server platform
> > would ease the work on the client side ?
> 
> I don't see easy way to avoid work on the client side. However the Java
> Bluetooth programming is not that big deal (RFCOMM channels only) from
> what I heard. I never did it and so I might be wrong.

JSR-82 (Java APIs for Bluetooth) provides access to L2CAP, RFCOMM and
OBEX. You don't get OBEX on Symbian OS v7.0s though. Quite a lot of
phones provide it these days.

Cheers,
Steve
-- 
Stephen Crane <jscrane@maths.tcd.ie>

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

      reply	other threads:[~2006-01-11 19:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-11  9:36 [Bluez-devel] Developing a basic service for BlueTooth enabled devices Blue Hammer
2006-01-11 14:29 ` Marcel Holtmann
2006-01-11 19:10   ` Stephen Crane [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=1137006621.7489.20.camel@localhost.localdomain \
    --to=jscrane@maths.tcd.ie \
    --cc=bluez-devel@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;
as well as URLs for NNTP newsgroup(s).