From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] [PATCH] dbus.c cleanup
Date: Tue, 01 Nov 2005 20:58:19 +0100 [thread overview]
Message-ID: <1130875099.5048.17.camel@blade> (raw)
In-Reply-To: <e1effdeb0511011108v13f75f08i6291e266eb235a34@mail.gmail.com>
Hi Claudio,
> here is patch to move the find_conn function to lib.c file.
I just realized that I already moved it out of dbus.c and so lets keep
it in hcid as inline function for now.
> Regarding the error related functions, can I move to a error.c file or
> it's better keep them in the dbus.c?
At the moment, I think it is better to keep them there. I don't have any
real opinion at the moment and so it might be better not to move to much
code around.
> Another point is the Disconnect signal. Which approach you preffer
> exit or create a timer to re-connect each x seconds?
We should try to re-connect. The security is still running and so we
can't exit.
> IMHO, I think it not necessary handle this scenario. Restart the
> dbus-daemon is not common.
Every time you update your D-Bus installation. The Ubuntu guys even
popup a message box that you should reboot your system ;)
Regards
Marcel
-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2005-11-01 19:58 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-29 17:53 [Bluez-devel] [PATCH] dbus.c cleanup Johan Hedberg
2005-10-29 18:07 ` Marcel Holtmann
2005-10-29 18:48 ` Johan Hedberg
2005-10-29 19:07 ` Marcel Holtmann
2005-10-31 11:59 ` Claudio Takahasi
2005-10-31 12:07 ` Johan Hedberg
2005-10-31 12:14 ` Marcel Holtmann
2005-10-31 12:30 ` Eduardo Rocha
2005-10-31 12:12 ` Marcel Holtmann
2005-10-31 13:47 ` Claudio Takahasi
2005-11-01 13:11 ` Marcel Holtmann
2005-11-01 13:21 ` Claudio Takahasi
2005-11-01 19:08 ` Claudio Takahasi
2005-11-01 19:58 ` Marcel Holtmann [this message]
2005-11-01 20:23 ` Johan Hedberg
2005-11-01 20:40 ` Marcel Holtmann
2005-11-01 20:53 ` Claudio Takahasi
-- strict thread matches above, loose matches on Subject: below --
2005-11-03 7:20 Johan Hedberg
2005-11-03 8:34 ` Marcel Holtmann
2005-11-03 8:54 ` Johan Hedberg
2005-11-03 9:08 ` Marcel Holtmann
2005-11-03 9:23 ` Johan Hedberg
2005-11-03 9:41 ` Marcel Holtmann
2005-11-03 10:13 ` Johan Hedberg
2005-11-03 10:33 ` Marcel Holtmann
2005-11-03 14:22 ` Johan Hedberg
2005-11-03 14:36 ` 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=1130875099.5048.17.camel@blade \
--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