linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] multiple rfcomm listeners
Date: Sun, 27 Nov 2005 22:47:06 +0100	[thread overview]
Message-ID: <1133128026.13629.18.camel@blade> (raw)
In-Reply-To: <438A21B2.40609@xmission.com>

Hi Brad,

> >>>I've heard that bluetooth clients are supposed to check for the SP
> >>>channel via sdp
> > this is a problem with the Bluetooth specification and its qualication.
> 
> this got me thinking that SP is the wrong service for gps. They should
> have chosen a protocol that allows for multiple simultaneous plain l2cap
> connections.
> 
> but... would it be possible for me to write an app that listens on an
> l2cap socket on the right psm and implements a pseudo-rfcomm protocol
> that allows for multiple simultaneous connections? if it can be done,
> then sdp would just advertise a single SP service and multiple clients
> could use it. they wouldn't even know about the fakery.

the L2CAP supports multiple connections to the same PSM from the same
device (you need this for AVDTP). For RFCOMM these connections must come
from a different device. Meaning that the underlying L2CAP link must be
different.

Actually the concept of RFCOMM was bad in the first place, because an
L2CAP with flow control would have been solved almost everything.

> it would be sort of gross, but as long as it doesn't require surgery to
> the stack or unloading rfcomm.ko, it wouldn't be that bad, eh?

You can do whatever you like. Use UUID-128 to identify your service and
use PSM numbers starting with 4097 (0x1001).

Regards

Marcel




-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2005-11-27 21:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-27  6:42 [Bluez-devel] multiple rfcomm listeners Brad Midgley
2005-11-27 14:05 ` Peter Wippich
2005-11-27 18:33   ` Marcel Holtmann
2005-11-27 21:14     ` Brad Midgley
2005-11-27 21:47       ` Marcel Holtmann [this message]
2005-11-27 21:59         ` Brad Midgley
2005-11-27 22:08           ` Marcel Holtmann
2005-11-27 22:25             ` Brad Midgley
2005-11-27 23:19               ` 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=1133128026.13629.18.camel@blade \
    --to=marcel@holtmann.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 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).