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: Tue, 08 Jul 2008 22:41:34 +0200 [thread overview]
Message-ID: <1215549694.26279.6.camel@californication> (raw)
In-Reply-To: <48728258.6080809@aircable.net>
Hi Manuel,
> I've been asking this the hole weekend on the irc channel, but yet no
> one could tell me if this is a bug or a feature, or what ever.
>
> On Dbus api 3.X you could register binary sdp records over dbus, but new
> api can't I all ready implemented adding records, I need to implement
> the update records. But I would like to know if it makes sense to commit
> this patch or not.
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.
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
next prev parent reply other threads:[~2008-07-08 20:41 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 ` Marcel Holtmann [this message]
2008-07-08 19:10 ` [Bluez-devel] " Manuel Naranjo
2008-07-09 0:26 ` 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=1215549694.26279.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