Linux bluetooth development
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@rvs.uni-bielefeld.de>
To: Max Krasnyansky <maxk@qualcomm.com>
Cc: Stephen Crane <steve.crane@rococosoft.com>,
	Philip Blundell <pb@nexus.co.uk>,
	BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: [Bluez-devel] Re: Version 3 libs/utils
Date: 18 Jul 2003 02:33:34 +0200	[thread overview]
Message-ID: <1058488421.25379.116.camel@pegasus> (raw)
In-Reply-To: <5.1.0.14.2.20030717170310.0703eec8@unixmail.qualcomm.com>

Hi Max,

> >> What about a Bluetooth daemon (for exmaple btmgr) which integrates the
> >> security manager and the sdpd. It can also store an userspace Bluetooth
> >> inquiry cache, name database and remote SDP cache. The local
> >> configuration (like local device name) for example can also modified
> >> through this daemon and restored on next boot, which is good for
> >> handheld devices. The access can be done through a defined protocol over
> >> unix sockets.
> >
> >I quite like this idea, except the SDP server functionality won't be
> >needed for some devices (e.g., handhelds).
> Agreed.

not agreed.

Try to connect with a Windows machine to a Linux based handheld to
transfer files over OBEX. You need a SDP server on your Linux handheld.
Only the real client only devices need no SDP server and these are
special cases or applications.

Regards

Marcel




-------------------------------------------------------
This SF.net email is sponsored by: VM Ware
With VMware you can run multiple operating systems on a single machine.
WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines at the
same time. Free trial click here: http://www.vmware.com/wl/offer/345/0
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2003-07-18  0:33 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-01  0:03 Version 3 libs/utils Max Krasnyansky
2003-07-02  1:01 ` [Bluez-devel] " Marcel Holtmann
2003-07-02  8:34   ` Stephen Crane
2003-07-02 16:29     ` [Bluez-devel] " Marcel Holtmann
2003-07-18  0:19       ` Max Krasnyansky
2003-07-18  0:10     ` Max Krasnyansky
2003-07-18  0:33       ` Marcel Holtmann [this message]
2003-07-22  0:32         ` [Bluez-devel] " Max Krasnyansky
2003-07-22 10:06           ` Marcel Holtmann
2003-07-18  0:00   ` Max Krasnyansky
2003-07-18  0:51     ` [Bluez-devel] " Marcel Holtmann
2003-07-22  0:44       ` Max Krasnyansky
2003-07-22 10:40         ` Marcel Holtmann
2003-07-22 20:05           ` Max Krasnyansky
2003-07-22 21:33             ` Marcel Holtmann
2003-07-23 16:27               ` Max Krasnyansky

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=1058488421.25379.116.camel@pegasus \
    --to=marcel@rvs.uni-bielefeld.de \
    --cc=bluez-devel@lists.sourceforge.net \
    --cc=maxk@qualcomm.com \
    --cc=pb@nexus.co.uk \
    --cc=steve.crane@rococosoft.com \
    /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