From: "Gustavo F. Padovan" <gustavo@padovan.org>
To: "Zhang, Zhenhua" <zhenhua.zhang@intel.com>
Cc: "linux-bluetooth@vger.kernel.org" <linux-bluetooth@vger.kernel.org>
Subject: Re: [PATCH] Dial-up Networking profile API
Date: Sun, 16 May 2010 23:18:29 -0300 [thread overview]
Message-ID: <20100517021829.GG23754@vigoh> (raw)
In-Reply-To: <33AB447FBD802F4E932063B962385B351E79EBA6@shsmsx501.ccr.corp.intel.com>
Hi Zhenhua,
* Zhang, Zhenhua <zhenhua.zhang@intel.com> [2010-05-10 08:41:59 +0800]:
...
> > +DUNAgent hierarchy
> > +===============
> > +
> > +Service unique name
> > +Interface org.bluez.DUNAgent
> > +Object path freely definable
> > +
> > +Methods void NewConnection(filedescriptor fd)
> > +
> > + This method gets called whenever a new DUN
> > + connection has been established. The objectpath
> > + contains the object path of the remote
> > device. This
> > + method assumes that DBus daemon with
> > file descriptor
> > + passing capability is being used.
> > +
> > + The agent should only return
> > successfully once the
> > + establishment of the data call has been fineshed
>
> A typo 'fineshed' should be 'finished'.
Thanks. ;)
>
> > + without problems.
> > +
> > + Possible Errors:
> > org.bluez.Error.InvalidArguments
> > + org.bluez.Error.Failed
> > +
> > + void Release()
> > +
> > + This method gets called whenever the service daemon
> > + unregisters the agent.
>
> Compared with hfp-api.txt, I think we should also add the sentence like "or whenever the Adapter where the DUNAgent registers itself is removed".
Or we can remove that sentence from hfp-api, since when a adapter is
removed bluetoothd relaese all agents on that adapter.
Regards,
--
Gustavo F. Padovan
http://padovan.org
next prev parent reply other threads:[~2010-05-17 2:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-09 2:11 [PATCH] Dial-up Networking profile API Gustavo F. Padovan
2010-05-10 0:41 ` Zhang, Zhenhua
2010-05-17 2:18 ` Gustavo F. Padovan [this message]
2010-05-17 2:20 ` Zhang, Zhenhua
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=20100517021829.GG23754@vigoh \
--to=gustavo@padovan.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=zhenhua.zhang@intel.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