public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrea Carlevato <andrea.carlevatoml@gmail.com>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] sdp_connect, how to make it shorter ?
Date: Wed, 7 Sep 2005 15:43:04 +0200	[thread overview]
Message-ID: <becc9d2c05090706433d62924b@mail.gmail.com> (raw)
In-Reply-To: <1125922154.11955.17.camel@pegasus>

[-- Attachment #1: Type: text/plain, Size: 1204 bytes --]

ok, so what value can i use instead of SDP_RETRY_IF_BUSY ?

thanks a lot
Andrea



On 9/5/05, Marcel Holtmann <marcel@holtmann.org> wrote:
> 
> Hi Andrea,
> 
> > i need to browse a set of random bt device for
> > a specific sdp profile. So use a function like
> > the "do_search" of sdptool.
> > But when an inquired bt device does not
> > aswer the request, the sdp_connect tries
> > for a long time to estabilish a connection,
> > and this is bad for my project.
> > How can i make much shorter the the sdp_connect
> > timeout ?
> 
> don't use the SDP_RETRY_IF_BUSY flag in sdp_connect().
> 
> Regards
> 
> Marcel
> 
> 
> 
> 
> -------------------------------------------------------
> SF.Net email is Sponsored by the Better Software Conference & EXPO
> September 19-22, 2005 * San Francisco, CA * Development Lifecycle 
> Practices
> Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
> Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
> _______________________________________________
> Bluez-devel mailing list
> Bluez-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-devel
>

[-- Attachment #2: Type: text/html, Size: 1722 bytes --]

  reply	other threads:[~2005-09-07 13:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-30 13:46 [Bluez-devel] sdp_connect, how to make it shorter ? Andrea Carlevato
2005-09-05 12:09 ` Marcel Holtmann
2005-09-07 13:43   ` Andrea Carlevato [this message]
2005-09-07 14:12     ` 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=becc9d2c05090706433d62924b@mail.gmail.com \
    --to=andrea.carlevatoml@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