public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: "Jan Benes" <jbenes@gmail.com>
To: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] sdp_connect and co, timing
Date: Sun, 16 Apr 2006 18:01:54 +0200	[thread overview]
Message-ID: <a3b1b800604160901k6e86614bueceba1bcd5466d5d@mail.gmail.com> (raw)

hello,
I'm trying ot write an application that scans for devices, asks for
name and services and eventually sends some files/data. I'm running in
threads. I've already discovered that I must use exclusive access to
the dongle during connection-time. I also don't do any connecting
while asking for services or scanning for devices. Still, sometimes,
the sdp_connect fails to connect for some time. Also, rarely, the
inquiry fails. Is it possible that there needs to be some time gap
between such requests? Do scanning/asking for
services/connectiong/sending cause "collisions"?

PS: also, what are the possible responses from a sdp_connect (or the
respective socket functinos from the function itself. I can't find
them anywhere)

thanks, Jan


-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

             reply	other threads:[~2006-04-16 16:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-16 16:01 Jan Benes [this message]
2006-04-18 12:08 ` [Bluez-devel] sdp_connect and co, timing Amateur

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=a3b1b800604160901k6e86614bueceba1bcd5466d5d@mail.gmail.com \
    --to=jbenes@gmail.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