From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] dbus-sdp & find_pending_connect
Date: Thu, 15 Feb 2007 09:10:55 +0100 [thread overview]
Message-ID: <1171527055.28302.8.camel@violet> (raw)
In-Reply-To: <200702151021.56853.denis.kenzior@trolltech.com>
Hi Denis,
> I'd like to understand why all SDP related functions in dbus-sdp.c call the
> find_pending_connect function?
>
> Effectively this guards against simultaneous SDP connection attempts to the
> same remote device. My understanding is that BlueZ does not have any
> limitations against multiple simultaneous connections to the same device, and
> neither does the BlueZ sdp daemon. Commenting out find_pending_connect, I
> can run up to 6 simultaneous SDP queries to another BlueZ implementation
> (this is because sdpd has a queue of up to 5 connections.) So this leads me
> to wonder why hcid is not allowing this particular case?
actually I have no idea and I didn't write that piece of code. There
shouldn't be any limitations, but not all remote SDP implementation can
deal with concurrent requests and so we have to be careful.
Regards
Marcel
-------------------------------------------------------------------------
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
prev parent reply other threads:[~2007-02-15 8:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-15 0:21 [Bluez-devel] dbus-sdp & find_pending_connect Denis KENZIOR
2007-02-15 8:10 ` 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=1171527055.28302.8.camel@violet \
--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 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.