From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] SDP over XML
Date: Thu, 19 Oct 2006 11:12:33 +0200 [thread overview]
Message-ID: <1161249153.27710.5.camel@localhost> (raw)
In-Reply-To: <200610191334.25362.denis.kenzior@trolltech.com>
Hi Denis,
> I've been playing around with the idea of encapsulating SDP information over
> XML. The primary aim was to enable things like sdptool or hcid to be able to
> exchange SDP records in an open format. It would also enable for
> applications to register arbitrary SDP records without relying on the sdp
> library (it is GPLed and thus not useable to some people)
any SDP record registration will have to go over D-Bus in the future and
it will come along with the service registration feature. However none
of this has been set into to stone yet.
> I wrote some code for producing and parsing XML SDP records. The aim would be
> to replace the current hcid GetRemoteServiceRecord method with something that
> produces XML, and also to have something like a RegisterServiceRecord that
> would take either a string description (e.g. OPUSH) and
> RegisterServiceRecordXML that would take an XML string.
The RegisterService... part is under discussion at the moment and I have
no idea how the final outcome will look like. I am okay with having an
additional method that returns the SDP service record in XML format, but
first you would have to define the DTD for it and we have to agree on
it.
> Additionally, a lot of the code that is currently in sdptool.c could be
> refactored into XML files, and it would be much more trivial to add new
> profiles (e.g. as an XML template instead of a function inside sdptool)
The record add function of sdptool is actually more a development thing,
than something you should use in real applications. However I am against
adding a dependency on a XML parsing library to sdptool.
Regards
Marcel
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2006-10-19 9:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-19 3:34 [Bluez-devel] SDP over XML Denis KENZIOR
2006-10-19 9:12 ` Marcel Holtmann [this message]
2006-10-20 1:27 ` Denis KENZIOR
2006-10-20 2:33 ` Marcel Holtmann
2006-10-20 10:30 ` P. Durante
2006-10-20 10:41 ` Marcel Holtmann
2006-10-20 11:32 ` P. Durante
2006-10-19 10:13 ` Peter Wippich
2006-10-19 17:08 ` Albert Huang
2006-10-20 10:50 ` Peter Wippich
2006-10-20 10:53 ` 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=1161249153.27710.5.camel@localhost \
--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