From: Daniel Abraham <daniel.shrugged@gmail.com>
To: linux-bluetooth@vger.kernel.org
Subject: Re: no client session close in obexd 0.23?
Date: Mon, 26 Apr 2010 13:39:22 +0300 [thread overview]
Message-ID: <x2z2c3916b71004260339j3cd86068g3b4adf5cd523c450@mail.gmail.com> (raw)
In-Reply-To: <r2h2c3916b71004260229p48a39235m917ee7ebb0006efe@mail.gmail.com>
Oops, didn't notice the (also new) client method "RemoveSession"
Out of curiosity, what's the benefit of moving close/remove from
session scope to client scope?
On Mon, Apr 26, 2010 at 12:29 PM, Daniel Abraham
<daniel.shrugged@gmail.com> wrote:
> I noticed that the client session close method is missing in obexd 0.23
> (and also from the API document, so I guess it's intentional)
>
> So how can I trigger it?
>
> Thanks
>
next prev parent reply other threads:[~2010-04-26 10:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-26 9:29 no client session close in obexd 0.23? Daniel Abraham
2010-04-26 10:39 ` Daniel Abraham [this message]
2010-04-26 18:24 ` Luiz Augusto von Dentz
2010-04-26 23:37 ` Daniel Abraham
2010-04-27 7:10 ` Luiz Augusto von Dentz
2010-04-27 10:35 ` Daniel Abraham
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=x2z2c3916b71004260339j3cd86068g3b4adf5cd523c450@mail.gmail.com \
--to=daniel.shrugged@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).