From: Marcel Holtmann <marcel@holtmann.org>
To: Antonio Terreno <antonio.terreno@gmail.com>
Cc: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] concurrent service searches
Date: Mon, 29 May 2006 15:34:20 +0200 [thread overview]
Message-ID: <1148909660.31689.62.camel@localhost> (raw)
In-Reply-To: <100466c40605161025y72f1d718j1e4868a2ebbd3db6@mail.gmail.com>
Hi Antonio,
> > > why if I start multiple services search on different devices (always
> > > less than 7)
> > >
> > > in that way:
> > > sdptool browse "DEVICE_ADDR"
> > > [gnome-obex-send --dest "DEVICE_ADDR" file2send.txt] (optional)
> > >
> > > I get always errors (on 4-5 devices is fine, on 3-2 devices is "Failed
> > > to connect to SDP server on "DEVICE_ADDR": File descriptor in bad
> > > state")
> > >
> > > The situation is better if I wait 1 or even 2 sec before starting a
> > > new search and send.
> > >
> > > The problem was triggered developing a multithreaded bluetooth server
> > > in java, with avetana bluetooth.
> > > I dont have these problem using the same code on windows....
> >
> > you can't have multiple inquiry or page attempts at the same time. This
> > is a limitation of the baseband and not the host.
>
> Baseband limitation? And why on windows looks working? The inquiries
> are somehow "buffered"?
> And why if I put a sleep on my code/script looks also working?
> Maybe cos the Search4Services are already terminated?
>
> At this point, assuming that we can do just one service discovery&obex
> push by time what about putting 10 antennas and do one discovery for
> each antenna?
>
> And if it's stupid to have 10 antennas, is it possible to have 7
> concurrent object push at the same time or it's always the baseband
> problem?
you can have only an inquiry or a page at the same time. That is
different. Once the connection has been established then you can run
another inquiry or create a second connection (with almost every modern
chips).
So if you have a connection (ACL link) you can run as many upper layer
protocols (SDP, RFCOMM, OBEX etc.) as you like on it. They are all
multiplexed and this is done by the Bluetooth subsystem of the Linux
kernel.
However we don't buffer inquiry or page requests. If the fail, they fail
and we don't try again.
Regards
Marcel
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2006-05-29 13:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-16 17:25 [Bluez-devel] concurrent service searches Antonio Terreno
2006-05-29 13:34 ` Marcel Holtmann [this message]
2006-05-30 18:20 ` Antonio Terreno
-- strict thread matches above, loose matches on Subject: below --
2006-05-15 8:15 Antonio Terreno
2006-05-12 17:19 Antonio Terreno
2006-05-16 14:23 ` 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=1148909660.31689.62.camel@localhost \
--to=marcel@holtmann.org \
--cc=antonio.terreno@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