From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] sdpd doesn't always collect non-persistent service records
Date: Mon, 23 Jun 2008 03:12:24 +0200 [thread overview]
Message-ID: <1214183544.7046.32.camel@violet> (raw)
In-Reply-To: <ef9938ec0806121252p17878962x186ef28e81b1a86c@mail.gmail.com>
Hi Albert,
> When using the libbluetooth SDP API, records registered that do not
> have SDP_RECORD_PERSIST are not always collected by sdpd when the sdp
> session is closed. I think the attached patch should help.
thanks for the patch. I had to simplify it a little bit, but I finally
got around in committing it.
Regards
Marcel
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2008-06-23 1:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-12 19:52 [Bluez-devel] sdpd doesn't always collect non-persistent service records Albert Huang
2008-06-23 1:12 ` Marcel Holtmann [this message]
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=1214183544.7046.32.camel@violet \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
/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