From: Malte Steiner <steiner@mobileart.org>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Multithread Service Discovery
Date: Sun, 01 Apr 2007 16:04:43 +0200 [thread overview]
Message-ID: <1175436283.12319.9.camel@localhost> (raw)
In-Reply-To: <BAY124-W5118C7F2144DA03833009AF0610@phx.gbl>
Hi,
the choice of C++ and an object orientated approach was more done by my
customer. It has some benefits, e.g. regarding encapsulating data and
functionality but didnt made life easier in the first place. Bluez and
OpenObex is C and gave me some headaches with the callback routines for
instance.
I use threading for the whole application, not only or particulary for
the SDP discovery. And in general the multitasking solution at least
feels faster than the single task one.
You want to use Push instead of Put or FTP, Push is the only Obex
service which doesnt need pairing.
Cheers,
Malte
-------------------------------------------------------------------------
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
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2007-04-01 14:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-01 10:25 [Bluez-users] Multithread Service Discovery Robert Rawlins
2007-04-01 12:58 ` Marcel Holtmann
2007-04-01 14:04 ` Malte Steiner [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-04-01 14:00 Robert Rawlins
2007-03-31 19:58 Robert Rawlins
2007-03-31 20:44 ` Loreno Oliveira
2007-04-01 7:01 ` Marcel Holtmann
2007-03-30 19:33 Robert Rawlins
2007-03-30 19:45 ` Malte Steiner
2007-03-31 13:44 ` 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=1175436283.12319.9.camel@localhost \
--to=steiner@mobileart.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.