All of lore.kernel.org
 help / color / mirror / Atom feed
From: Max Krasnyansky <maxk@qualcomm.com>
To: Stephen Crane <steve.crane@rococosoft.com>
Cc: bluez-devel@lists.sourceforge.net, marcel@rvs.uni-bielefeld.de
Subject: Re: [Bluez-devel] RFComm channel allocation
Date: Thu, 09 Oct 2003 10:58:11 -0700	[thread overview]
Message-ID: <5.1.0.14.2.20031009104846.0591fb08@unixmail.qualcomm.com> (raw)
In-Reply-To: <1065696705.30376.257.camel@baroque.rococosoft.com>

At 03:51 AM 10/9/2003, Stephen Crane wrote:
>On Thu, 2003-10-09 at 01:52, Max Krasnyansky wrote:
>> >On a related matter (and I'm pretty sure this /has/ come up before),
>> >would it be possible to perform automatic channel allocation in the
>> >kernel? 0 would be a good distinguishing value for this (since it is
>> >reserved to the RFComm multiplexer).
>> It's possible but does not seem to be needed. I mean so far nobody had
>> a strong argument why we need to support it.
>
>It seems to me that we're moving towards a more service-oriented view
>where Bluetooth services are discovered by UUID rather than assuming
>they live at a fixed port/channel number. 
>
>If this is the case, servers shouldn't have to care what port/channel is
>used, they just bind to any and use getsockname() to find out the actual
>one allocated by the kernel, for subsequent advertisement by SDP. (Also
>this is possible for AF_INET sockets, so it wouldn't violate the
>principle of least surprise.)

Well the thing is PSM 0 and Channel 0 are already used for bind() on the 
client side. It means "I do not need a port". Unlike IP clients Bluetooth 
clients do not need unique port.

Max

      reply	other threads:[~2003-10-09 17:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1062078007.1823.33.camel@baroque.rococosoft.com>
2003-10-09  0:52 ` [Bluez-devel] RFComm channel allocation Max Krasnyansky
2003-10-09 10:51   ` Stephen Crane
2003-10-09 17:58     ` Max Krasnyansky [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=5.1.0.14.2.20031009104846.0591fb08@unixmail.qualcomm.com \
    --to=maxk@qualcomm.com \
    --cc=bluez-devel@lists.sourceforge.net \
    --cc=marcel@rvs.uni-bielefeld.de \
    --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 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.