From: Nils Faerber <nils.faerber@kernelconcepts.de>
To: Anthony Yulo <strikewing16th@hotmail.com>
Cc: bluez-devel@lists.sourceforge.net, blueinfo@yahoogroups.com
Subject: Re: [Bluez-devel] Bluetoooth and Threads?
Date: Fri, 09 Jan 2004 14:38:07 +0100 [thread overview]
Message-ID: <1073655487.989.50.camel@localhost> (raw)
In-Reply-To: <Law11-F108gLzhVOJwn00013a60@hotmail.com>
Am Fr, den 09.01.2004 schrieb Anthony Yulo um 04:38:
> Hi!
Hi!
> I'm just wondering if multiple threads can have their own bluetooth stack?
Errrmm... several *stacks* ??
Do you use several IP stacks for several IP connections??
I don't...
> I'm planning of a single program that uses threads, one thread does only
> device discovery.. and then store the devices on a list/queue.. and then
> maybe a couple of threads that reads from the queue and send data from the
> devices on the queue using RFCOMM.. maybe i can have seven threads since
> this is the maximum number bluetooth allows...
> is this possible?
Sure, perfectly possible.
You simply open the appropriate sockets in each thread and that's it.
CU
nils faerber
--
kernel concepts Tel: +49-271-771091-12
Dreisbachstr. 24 Fax: +49-271-771091-19
D-57250 Netphen D1 : +49-170-2729106
--
-------------------------------------------------------
This SF.net email is sponsored by: Perforce Software.
Perforce is the Fast Software Configuration Management System offering
advanced branching capabilities and atomic changes on 50+ platforms.
Free Eval! http://www.perforce.com/perforce/loadprog.html
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2004-01-09 13:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-09 3:38 [Bluez-devel] Bluetoooth and Threads? Anthony Yulo
2004-01-09 13:38 ` Nils Faerber [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=1073655487.989.50.camel@localhost \
--to=nils.faerber@kernelconcepts.de \
--cc=blueinfo@yahoogroups.com \
--cc=bluez-devel@lists.sourceforge.net \
--cc=strikewing16th@hotmail.com \
/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