All of lore.kernel.org
 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: [PATCH obexd v2 00/11] Support user defined headers in gwobex
Date: Wed, 22 Jun 2011 00:24:14 +0200	[thread overview]
Message-ID: <1308695065-3784-1-git-send-email-adamek.kuba@gmail.com> (raw)

Hi,

these patches will enable sending and receiving of user defined headers
in gwobex.

Two new functions will enable to start an asynchronous get or put
transfer, taking as an argument a list of structures describing
the headers to be sent. The headers are sent out in the order
of appearance on the list.

Likewise all response headers that would have been previously ignored
by gwobex are now inserted to a list in the current gw_obex_xfer
object, and so can be retrieved later after the asynchrous transfer
has finished.

Additionally, the order of sending headers in gwobex is changed
to the one mandated by BIP, i.e.:
Connection ID->Type->Name->Application Parameters->User Defined Headers.

This series incorporates Luiz's changes.

Jakub Adamek (11):
  Add a_header struct for additional header data
  Add list to store received headers
  Add function to create fresh a_header
  Store received headers in gw_obex_xfer object
  Add functions to get, put w. a_header list
  Parse headers in a PUT response packet
  Add functions for async requests w a_header list
  Reorder headers to conform to BIP's requirements
  Handle partial content response from server
  Convenience method to make deep copy of a_header
  Add func for fetching header by id from list

 gwobex/gw-obex.h   |   39 +++++++++++++++
 gwobex/obex-priv.c |  135 +++++++++++++++++++++++++++++++++++----------------
 gwobex/obex-priv.h |   29 +++++++++++
 gwobex/obex-xfer.c |   97 +++++++++++++++++++++++++++++++++++++
 gwobex/obex-xfer.h |   18 +++++++
 5 files changed, 275 insertions(+), 43 deletions(-)


             reply	other threads:[~2011-06-21 22:24 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-21 22:24 Jakub Adamek [this message]
2011-06-21 22:24 ` [PATCH obexd v2 01/11] Add a_header struct for additional header data Jakub Adamek
2011-06-21 22:24 ` [PATCH obexd v2 02/11] Add list to store received headers Jakub Adamek
2011-06-21 22:24 ` [PATCH obexd v2 03/11] Add function to create fresh a_header Jakub Adamek
2011-06-22  7:05   ` Luiz Augusto von Dentz
2011-06-21 22:24 ` [PATCH obexd v2 04/11] Store received headers in gw_obex_xfer object Jakub Adamek
2011-06-21 22:24 ` [PATCH obexd v2 05/11] Add functions to get, put w. a_header list Jakub Adamek
2011-06-21 22:24 ` [PATCH obexd v2 06/11] Parse headers in a PUT response packet Jakub Adamek
2011-06-21 22:24 ` [PATCH obexd v2 07/11] Add functions for async requests w a_header list Jakub Adamek
2011-06-21 22:24 ` [PATCH obexd v2 08/11] Reorder headers to conform to BIP's requirements Jakub Adamek
2011-06-21 22:24 ` [PATCH obexd v2 09/11] Handle partial content response from server Jakub Adamek
2011-06-21 22:24 ` [PATCH obexd v2 10/11] Convenience method to make deep copy of a_header Jakub Adamek
2011-06-21 22:24 ` [PATCH obexd v2 11/11] Add func for fetching header by id from list Jakub Adamek
2011-06-22  7:33 ` [PATCH obexd v2 00/11] Support user defined headers in gwobex Luiz Augusto von Dentz
2011-06-22  7:35   ` Luiz Augusto von Dentz

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=1308695065-3784-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.