From: "José Antonio Santos Cadenas" <jcaden@libresoft.es>
To: "Elvis Pfützenreuter" <epx@signove.com>
Cc: "João Paulo Rechi Vita" <jprvita@gmail.com>,
"Gustavo F. Padovan" <gustavo@padovan.org>,
"linux-bluetooth@vger.kernel.org"
<linux-bluetooth@vger.kernel.org>
Subject: Re: Data transmission and reconnections in HDP
Date: Mon, 10 May 2010 09:53:57 +0200 [thread overview]
Message-ID: <201005100953.57556.jcaden@libresoft.es> (raw)
In-Reply-To: <536E0C33-0FB5-4A71-AE8A-5C96F2ABEA0F@signove.com>
El Monday 10 May 2010 04:31:22 Elvis Pfützenreuter escribió:
> >
> > Automatic reconnection should happen only in the case HDP has
> > disconnected the transport for power-saving, because the data layer is
> > idle, doesn't it? So will (b) ever happen? In the case the connection
> > is dropped (loss of signal etc) the data layer should always be
> > notified IMO (case c).
>
> MCAP spec says that
>
> "Because the Source and Sink assign a unique MDL ID when a new MDL is formed, using this same ID later allows a reconnection to the same context after they are intentionally
closed or unintentionally broken (possibly from interference or temporarily moving out of range)." (Page 27)
>
> HDP spec always talks mentions "reconnection" and "power saving" near each other, but I guess it is in a broader context (not having to renegotiate every data channel after an
involuntary break-up also saves power).--
Completely agree with this, reconnections should be performed until the
data channel is deleted (this mdlid is no valid anymore for reconnections)
or until one of the sessions is closed, the remote or the local.
next prev parent reply other threads:[~2010-05-10 7:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-07 11:02 Data transmission and reconnections in HDP José Antonio Santos Cadenas
2010-05-07 12:08 ` Gustavo F. Padovan
2010-05-07 18:25 ` João Paulo Rechi Vita
2010-05-07 18:39 ` Santiago Carot-Nemesio
2010-05-07 18:49 ` João Paulo Rechi Vita
2010-05-07 19:57 ` Gustavo F. Padovan
[not found] ` <8D8F1AA1-A7C1-4636-BB75-1EF1A2E1A556@signove.com>
2010-05-10 1:08 ` João Paulo Rechi Vita
2010-05-10 2:31 ` Elvis Pfützenreuter
2010-05-10 7:53 ` José Antonio Santos Cadenas [this message]
2010-05-10 7:47 ` José Antonio Santos Cadenas
[not found] ` <82D1897F-4DEE-47F9-BD00-57087F182C3D@signove.com>
2010-05-07 19:49 ` Gustavo F. Padovan
2010-05-07 19:55 ` Elvis Pfützenreuter
2010-05-07 20:17 ` Gustavo F. Padovan
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=201005100953.57556.jcaden@libresoft.es \
--to=jcaden@libresoft.es \
--cc=epx@signove.com \
--cc=gustavo@padovan.org \
--cc=jprvita@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
/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).