Linux bluetooth development
 help / color / mirror / Atom feed
From: Denis KENZIOR <denis.kenzior@trolltech.com>
To: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] DBus SDP API
Date: Thu, 23 Nov 2006 15:26:09 +1000	[thread overview]
Message-ID: <200611231526.09459.denis.kenzior@trolltech.com> (raw)

Marcel,

Three questions:

Have you given any more thought as to how the RFCOMM channels are managed by 
the DBus Service API?  The same goes for L2CAP.  From what I understand the 
current implementation depends on clients to know what is available...

Will there be a lower-level SDP registration framework for the local device?  
E.g. to be able to manually register records in binary/XML format without 
creating a service agent?

Most importantly, do you have plans for local versions of
                array{uint32} GetRemoteServiceHandles(string address, string 
match)

and

                array{byte} GetRemoteServiceRecord(string address, uint32 
handle)

?

-Denis

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

             reply	other threads:[~2006-11-23  5:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-23  5:26 Denis KENZIOR [this message]
2006-11-23  5:35 ` [Bluez-devel] DBus SDP API Marcel Holtmann
2006-11-23  5:52   ` Denis KENZIOR
2006-11-23  5:58     ` Marcel Holtmann
2006-11-23  6:33       ` Denis KENZIOR
2006-11-23  6:51         ` 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=200611231526.09459.denis.kenzior@trolltech.com \
    --to=denis.kenzior@trolltech.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox