linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Adamek <adamek.kuba@gmail.com>
To: linux-bluetooth@vger.kernel.org
Cc: Jakub Adamek <adamek.kuba@gmail.com>
Subject: [RFC obexd 0/4] Extend gobex high level transfer API
Date: Wed, 21 Dec 2011 02:40:59 +0100	[thread overview]
Message-ID: <1324431663-3800-1-git-send-email-adamek.kuba@gmail.com> (raw)

The purpose of this patch series is to propose an extension
to the current high level request transfer API.
The motivation for this is that currently profiles that require
parsing of non-body response headers in PUT operations
(such as BIP) can not use the high level transfer API.
The proposed solution is to make the function the API
uses to handle each response packet replaceable at the time
of transfer creation.
A custom handler can process incoming packets and (if desired)
pass them to the default packet handler in order
for it to proceed with the transfer.

Jakub Adamek (4):
  gobex: make transfer structure public and opaque
  gobex: make default response function public
  gobex: add response function parameter to API
  gobex: add functions to public transfer API

 client/transfer.c          |    6 +-
 gobex/gobex-transfer.c     |  122 ++++++++++++++++++++++++++-----------------
 gobex/gobex.h              |   16 +++++-
 unit/test-gobex-transfer.c |   20 ++++----
 4 files changed, 101 insertions(+), 63 deletions(-)

-- 
1.7.4.1


             reply	other threads:[~2011-12-21  1:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-21  1:40 Jakub Adamek [this message]
2011-12-21  1:41 ` [RFC obexd 1/4] gobex: make transfer structure public and opaque Jakub Adamek
2011-12-21  1:41 ` [RFC obexd 2/4] gobex: make default response function public Jakub Adamek
2011-12-21  1:41 ` [RFC obexd 3/4] gobex: add response function parameter to API Jakub Adamek
2011-12-21  1:41 ` [RFC obexd 4/4] gobex: add functions to public transfer API Jakub Adamek

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=1324431663-3800-1-git-send-email-adamek.kuba@gmail.com \
    --to=adamek.kuba@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).