From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] No more binary SDP registration in new 4.0 API?
Date: Wed, 09 Jul 2008 02:26:59 +0200 [thread overview]
Message-ID: <1215563219.4586.6.camel@californication> (raw)
In-Reply-To: <4873BB89.5030109@aircable.net>
Hi Manuel,
> > the idea is not to use binary SDP records at all anymore. Also we wanna
> > move the record registration and service authorization into a plugin and
> > don't have this in the Adapter interface anymore.
> >
> Ok got it. So then to work with binary records you should use bluelib
> right? Or this is going to be deprecated too?.
yes, the access via SDP Unix socket will also go away.
> Thing is that in cases like BIP you wanna work with binary stuff,
> embedding xml records in your code might not be a good idea at all.
>
> In fact the patch I created was to start making obex-data-server use the
> new API, but this was some how a boomer. What shall we do? Use sdplib,
> or go with xml strings?
I think the best is to move this all into a plugin and then we could
have a plugin that provides binary record registration. However I am not
a big fan of doing SDP without XML anymore. Building the record with the
current C function is painful and leads to errors or memory leaks.
Regards
Marcel
-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2008-07-09 0:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-07 20:53 [Bluez-devel] No more binary SDP registration in new 4.0 API? Manuel Naranjo
2008-07-08 3:25 ` [Bluez-devel] [PATCH] " Manuel Naranjo
2008-07-08 20:41 ` [Bluez-devel] " Marcel Holtmann
2008-07-08 19:10 ` Manuel Naranjo
2008-07-09 0:26 ` 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=1215563219.4586.6.camel@californication \
--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