From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] DBUS service support - Initial library
Date: Tue, 31 May 2005 01:05:45 +0200 [thread overview]
Message-ID: <1117494345.7072.235.camel@pegasus> (raw)
In-Reply-To: <e1effdeb050530154229f338a2@mail.gmail.com>
Hi Claudio,
> I am sending a new patch to be evaluated.
> Regarding glib dependency we need discuss this
> subject again. If you see the hcid code, there is a
> file (glib-ectomy.c) that implements the event
> processing, this code is a partial copy of glib.
>
> What do you prefer? Repeat the glib-ectomy.c code
> or use glib?
the glib-ectomy is only still there, because I was too lazy to replace
it with a clean main loop using poll() implementation.
> For Maemo, glib is not problem. It is included in
> the SDK.
This is not a valid argument. Creating a massive dependency chain is
always bad. Using Glib inside bluez-utils is no option.
> Regarding pthread I put two versions to be evaluated:
> 1. using pthread
> In my opinion because it save memory.
> http://www.indt.org.br/maemo/bluez/bluez-dbus-thread.diff
>
> 2. using fork
> In my opinion this is not a feasible approach
> because when listening is active two process
> will be running(a listening and another processing
> D-Bus messages).
> http://www.indt.org.br/maemo/bluez/bluez-dbus-fork.diff
Even without looking at the patches, I don't like any of it. I like to
see a nice main loop and then using poll(). We don't need threads or
forking out processes.
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by Yahoo.
Introducing Yahoo! Search Developer Network - Create apps using Yahoo!
Search APIs Find out how you can build Yahoo! directly into your own
Applications - visit http://developer.yahoo.net/?fr=offad-ysdn-ostg-q22005
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2005-05-30 23:05 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-28 20:00 [Bluez-devel] DBUS service support - Initial library Claudio Takahasi
2005-04-29 9:47 ` Marcel Holtmann
2005-04-29 12:26 ` Claudio Takahasi
2005-04-29 12:43 ` Marcel Holtmann
2005-04-29 22:20 ` Claudio Takahasi
2005-04-30 0:04 ` Marcel Holtmann
2005-05-01 21:16 ` Claudio Takahasi
2005-05-01 23:18 ` Marcel Holtmann
2005-05-02 15:32 ` Claudio Takahasi
2005-05-02 16:24 ` Marcel Holtmann
2005-05-09 21:31 ` Claudio Takahasi
2005-05-11 18:27 ` Marcel Holtmann
2005-05-12 9:00 ` Peter Wippich
2005-05-12 12:41 ` Marcel Holtmann
2005-05-12 16:21 ` Peter Wippich
2005-05-20 21:04 ` Claudio Takahasi
2005-05-23 10:27 ` Marcel Holtmann
2005-05-23 15:02 ` Claudio Takahasi
2005-05-24 9:07 ` Marcel Holtmann
2005-05-25 22:20 ` Claudio Takahasi
2005-05-26 9:08 ` Marcel Holtmann
2005-05-26 21:22 ` Claudio Takahasi
2005-05-26 21:40 ` Marcel Holtmann
2005-05-30 22:42 ` Claudio Takahasi
2005-05-30 23:05 ` Marcel Holtmann [this message]
2005-06-03 20:34 ` [Bluez-devel] DBUS service support - poll patch Claudio Takahasi
2005-06-03 20:38 ` Marcel Holtmann
2005-06-03 21:31 ` Claudio Takahasi
2005-06-03 22:10 ` Marcel Holtmann
2005-06-06 13:18 ` Claudio Takahasi
2005-06-14 11:37 ` Claudio Takahasi
2005-06-17 21:59 ` Claudio Takahasi
2005-06-18 23:28 ` Marcel Holtmann
2005-05-12 12:45 ` [Bluez-devel] DBUS service support - Initial library Claudio Takahasi
2005-05-12 16:23 ` Peter Wippich
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=1117494345.7072.235.camel@pegasus \
--to=marcel@holtmann.org \
--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