From: Stephen Crane <steve.crane@rococosoft.com>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Hi all !
Date: Fri, 26 Nov 2004 11:48:54 +0000 [thread overview]
Message-ID: <1101469734.16162.10.camel@baroque.rococosoft.com> (raw)
In-Reply-To: <41A6F456.5040005@prim-time.fr>
[-- Attachment #1: Type: text/plain, Size: 1221 bytes --]
Hi Xavier,
On Fri, 2004-11-26 at 10:16 +0100, Xavier Garreau wrote:
> >>I never used sdp api, did any of you wrote some white paper about
> >>bluetooth programming involving sdp (i found
> >>http://www.holtmann.org/papers/bluetooth/wtc2003_slides.pdf but it's not
> >>dealing with sdp)
> >
> > the programs dund and pand show you how to advertise a SDP record.
>
> Thank you very much Marcel, this was a useful answer, as usual !
>
> I just have another (amybe silly) question ...
>
> In bluez/pan/pand/sdp.c
> function bnep_sdp_register
>
> if sdp_record_register is succesful, the sdp_session is not closed
> whereas it is evrywhere else (when something fails).
>
> Does it means that sdp_record_register closes the sdp_session when it is
> successful ? That would mean we need to di sdp_connect foreach record we
> have to add (I know, we usually only have only one to do at a time, but
> that seems "strange" to me)
I think this is a bug. The session should always be explicitly closed.
Send in a patch :-)
> Regards !
> Xavier Garreau
Steve
--
Stephen Crane, Rococo Software Ltd. http://www.rococosoft.com
steve.crane@rococosoft.com +353-1-6601315 (ext 209)
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-11-26 11:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-25 16:12 [Bluez-devel] Hi all ! Xavier Garreau
2004-11-25 16:42 ` GUILLON Gabriel
2004-11-25 22:52 ` Marcel Holtmann
2004-11-26 9:16 ` Xavier Garreau
2004-11-26 11:48 ` Stephen Crane [this message]
2004-11-26 17:21 ` Marcel Holtmann
2004-11-26 9:18 ` Xavier Garreau
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=1101469734.16162.10.camel@baroque.rococosoft.com \
--to=steve.crane@rococosoft.com \
--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 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.