From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Cc: Claudio Takahasi <cktakahasi@gmail.com>
Subject: Re: [Bluez-devel] D-Bus tasks planning
Date: Wed, 18 Jan 2006 14:18:28 +0100 [thread overview]
Message-ID: <1137590308.27515.14.camel@localhost> (raw)
In-Reply-To: <1137569915.12927.9.camel@bluez.bueche.ch>
Hi Charles,
> > > I've just started planning the activities for this year. I would like
> > > receive feedbacks/comments about the items below. There are some tasks
> > > suggested and a lot of clouds :) I consider these tasks essential to
> > > make the D-Bus services usable and necessary to start the development
> > > of Network, Serial, HID, ... services over D-Bus.
> > >
> > > * Move hcid to bluetoothd
> >
> > since I don't wanna use threads,
> ...
>
> I'm not knowledgeable about threads in C and within bluez, but during my
> projects in Perl, I have found them a valuable asset. For my curiosity,
> what are the reasons behind your decision ?
since the bluetoothd should also run on any embedded system, it is a
good idea to not use thread, because they might not be as portable as an
event loop.
Regards
Marcel
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2006-01-18 13:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-17 13:35 [Bluez-devel] D-Bus tasks planning Claudio Takahasi
2006-01-17 13:49 ` Marcel Holtmann
2006-01-17 19:58 ` P. Durante
2006-01-17 22:53 ` Marcel Holtmann
2006-01-18 7:38 ` Charles Bueche
2006-01-18 13:18 ` Marcel Holtmann [this message]
2006-01-18 15:18 ` Charles Bueche
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=1137590308.27515.14.camel@localhost \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
--cc=cktakahasi@gmail.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;
as well as URLs for NNTP newsgroup(s).