All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Garrett <mjg59@srcf.ucam.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] [PATCH] implement RFCOMM Connect and Disconnect	methods
Date: Thu, 17 Aug 2006 12:41:16 +0100	[thread overview]
Message-ID: <20060817114116.GC5118@srcf.ucam.org> (raw)
In-Reply-To: <1155819858.4075.134.camel@aeonflux.holtmann.net>

On Thu, Aug 17, 2006 at 03:04:18PM +0200, Marcel Holtmann wrote:

> I haven't payed much attention to the RFCOMM parts of our D-Bus API
> since I declared it as experimental and it might still change. However
> one thing is that we wanna use strings. They are more flexible and if
> you use languages like Python they can come in handy.
> 
> In this case for example you might use "spp" (service name) or
> "0x10000" (record handle) to connect to a specific RFCOMM channel.

I'm not entirely clear on what a service name represents. Is it a 
specific service, or is it the profile implemented by that service? What 
string should represent non-standard services? As an example, my phone 
has a service called "Nokia OBEX PC Suite Services". If I want to use 
that via the DBus interface, I'll presumably need to use the record 
handle anyway?

> The SDP caching is still something that needs a lot of thinking before
> we will finally solve it. It is not as easy as people thing and always
> requesting a SDP record first is not a good idea either. However a lot
> of this depends on how broken the SDP records of the remote devices are.

I agree that always requesting the SDP record first is less than ideal, 
but I'd argue that it's better to have suboptimal functionality than no 
functionality :)

Thanks,
-- 
Matthew Garrett | mjg59@srcf.ucam.org

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2006-08-17 11:41 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-17 10:06 [Bluez-devel] [PATCH] implement RFCOMM Connect and Disconnect methods Matthew Garrett
2006-08-17 13:04 ` Marcel Holtmann
2006-08-17 11:41   ` Matthew Garrett [this message]
2006-08-17 11:59     ` Johan Hedberg
2006-08-17 12:01       ` Matthew Garrett
2006-08-19 14:36       ` Matthew Garrett
2006-08-20  1:39         ` Marcel Holtmann
2006-08-19 23:53           ` Matthew Garrett
2006-08-20  2:13             ` Marcel Holtmann
2006-08-20  0:31               ` Matthew Garrett
2006-08-20  3:15                 ` Marcel Holtmann
2006-08-20 17:59                   ` Matthew Garrett
2006-08-23  6:21                     ` [Bluez-devel] RFComm auth/encrypt Denis KENZIOR
2006-08-23 20:13                     ` [Bluez-devel] [PATCH] implement RFCOMM Connect and Disconnect methods Johan Hedberg

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=20060817114116.GC5118@srcf.ucam.org \
    --to=mjg59@srcf.ucam.org \
    --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 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.