public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Johan Hedberg <johan.hedberg@gmail.com>
To: BlueZ development <linux-bluetooth@vger.kernel.org>
Subject: Re: Add application header support to gwobex
Date: Sun, 19 Oct 2008 15:36:27 +0300	[thread overview]
Message-ID: <D94DFDBF-DAB1-4343-96F0-FFBA05A58373@gmail.com> (raw)
In-Reply-To: <1224404909.9386.29.camel@californication>

Hi Marcel,

On Oct 19, 2008, at 11:28, Marcel Holtmann wrote:
> for the PBAP support, we need to handle the application header and for
> our client/test applications, I extended gwobex to allow us to specify
> this header. What do you think?

Looks good to me, though the parameter lists to the _get and_put  
functions are starting to grow pretty long. In general it'd be nice to  
get the same functionality into libopenobex-glib soonish since I'm not  
particularly enjoying looking at this ancient code and coding style  
that should just die away ;)

Johan

  reply	other threads:[~2008-10-19 12:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-19  8:28 Add application header support to gwobex Marcel Holtmann
2008-10-19 12:36 ` Johan Hedberg [this message]
2008-10-19 17:00   ` Marcel Holtmann

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=D94DFDBF-DAB1-4343-96F0-FFBA05A58373@gmail.com \
    --to=johan.hedberg@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