From: Thomas Kear <qupada@initng.org>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] concurrent operations
Date: Tue, 21 Nov 2006 22:57:17 +1300 [thread overview]
Message-ID: <200611212257.25266.qupada@initng.org> (raw)
In-Reply-To: <b5dccebe0611210124h5076b396xa2e9c0617658cf13@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1573 bytes --]
You pretty much summed up everything there is to say. I see someone replied
off the list, but I'll add what I know, in any case.
As you noted, any regular data connection can be paired with others. The
limit is 7 connections, but you do have to remember that there's less than
800kbps to go around on Bluetooth 1.2 and only a couple of megabits on
Bluetooth 2.0. I have managed a file transfer from my cellphone (only ever
manages 25kB/s, ~200kbps) while talking on my bluetooth headset (not sure
about bandwidth use for it) but I don't think I'd like to test anything else
simultaneously.
--Thomas
On Tuesday 21 November 2006 10:24 pm, Mikael Lindqvist wrote:
> Hi,
>
> This is a general bluetooth question...
>
> I have been experimenting with bluetooth for some time now and I'm
> wondering what is actually possible to do simultaneously. My
> application is doing device discovery, service search and obex push.
> It seems as if it is possible to do several obex pushes at the same
> time (guess that would go for any kind of RFCOMM connections), but
> it's just possible to do one device discovery or one service search
> simultaneously. I. e. it's not possible to do service search at the
> same time as device discovery, and it's only possible to do service
> search for one remote device at the same time.
>
> So to sort things out once and for all, what is actually possible? And
> why does this limitation exist, is it something fundamental to
> bluetooth or just because of current implementations?
>
> -- Mikael
[-- Attachment #1.2: Type: application/pgp-signature, Size: 189 bytes --]
[-- Attachment #2: Type: text/plain, Size: 347 bytes --]
-------------------------------------------------------------------------
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
[-- Attachment #3: Type: text/plain, Size: 164 bytes --]
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
prev parent reply other threads:[~2006-11-21 9:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-21 9:24 [Bluez-users] concurrent operations Mikael Lindqvist
2006-11-21 9:29 ` Marcel Holtmann
2006-11-21 9:40 ` Mikael Lindqvist
2006-11-21 10:21 ` Peter Stephenson
2006-11-21 9:57 ` Thomas Kear [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=200611212257.25266.qupada@initng.org \
--to=qupada@initng.org \
--cc=bluez-users@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