From: "José Antonio Santos Cadenas" <santoscadenas@gmail.com>
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: Changes in HDP API
Date: Wed, 4 Aug 2010 19:53:40 +0200 [thread overview]
Message-ID: <201008041953.40795.santoscadenas@gmail.com> (raw)
In-Reply-To: <AANLkTinO4=BjcNP5uyi_nX0axaBth7aUAhgOoFdPKrY2@mail.gmail.com>
Hi,
El Wednesday 04 August 2010 18:45:50 Luiz Augusto von Dentz escribió:
> Hi,
>
> On Wed, Aug 4, 2010 at 4:54 PM, José Antonio Santos Cadenas
>
> <santoscadenas@gmail.com> wrote:
> >> This has 2 main advantages:
> >>
> >> 1. Anyone can request to connect not only applications which holds
> >> local endpoints
> >
> > How can you guess the remote end point to connect to if you don't have a
> > local end point?
>
> There is no endpoints involved in this case, bluetooth applet/agent
> has knowledge only of the device so bluetoothd will need to figure out
> all the matching endpoint and make sure local endpoint get notified
> about the available channels, so responding your question there is
> nothing to guess it all about matching the endpoints if there is no
> match it just fails after the discover as simple as that.
Sorry but I don't understand the answer. I think that the daemon needs to
guess the remote end point to connect to when the user performs a connection
of a data channel to a device (I mean the mdepid where the data channel will
be connected). In HDP each data channel can be configured in a specific way
(reliable or streaming) and is connected for an specific usage (that's the
data type parameter in the SDP record) so you have to specify this during the
connection of the channel.
An other thing to solve is the way that the data channel deletion is notified
if there is no associated agent, I mean, if you just do a Connect without
registering an agent first. This kind of events are supposed to be received by
the agent. An other special issue of HDP, data channels can be open or closed
but they are still active because reconnections are possible and this implies
no disconnection for the application layer.
>
> At least that is the idea around connect/disconnect in gnome-bluetooth
> and N900 bluetooth application does have a similar design.
I don't know how this is exactly working (I'll have a deeper look), but I
guess that only one agent is allowed. I think that will be great to have
multiple agents in HDP because more than one application can be using HDP at
the same time. I don't know if with only one agent this can be solved.
Regards
Jose.
next prev parent reply other threads:[~2010-08-04 17:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-04 7:49 Changes in HDP API Jose Antonio Santos Cadenas
2010-08-04 7:49 ` [PATCH] " Jose Antonio Santos Cadenas
2010-08-04 13:09 ` Luiz Augusto von Dentz
2010-08-04 13:54 ` José Antonio Santos Cadenas
2010-08-04 16:45 ` Luiz Augusto von Dentz
2010-08-04 17:53 ` José Antonio Santos Cadenas [this message]
2010-08-04 18:22 ` Elvis Pfützenreuter
2010-08-05 9:29 ` José Antonio Santos Cadenas
2010-08-05 13:49 ` [PATCH] " Jose Antonio Santos Cadenas
2010-08-09 10:33 ` Santiago Carot-Nemesio
2010-08-10 8:01 ` José Antonio Santos Cadenas
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=201008041953.40795.santoscadenas@gmail.com \
--to=santoscadenas@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.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;
as well as URLs for NNTP newsgroup(s).