[PATCH] do not call _dbus_warn_check_failed on checks
thiago at kde.org
Tue Nov 14 04:10:14 PST 2006
Daniel Stone wrote:
>> For another, there might be a lot of state kept in the applications
>> that may or may not be transferred to the new connection. This is
>> especially true for the unique connection names, which will be
>> restarted. Other problems also include race conditions when a call
>> comes in just after restart and the target wasn't yet present, etc.
>It's difficult, and you can never get it absolutely, perfectly,
>bullet-proof, 100% bug-free. But you can optimise for the common case
>and get it right 99.9% of the time. And when the planets align and
>conspire against you to cause one tiny minor failure in an extreme
>corner case, then it's still better than exit(3), which works for
>exactly 0.0% of the cases.
That is true.
But to reduce chance of error, the bus shouldn't be restarted unless
Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
PGP/GPG: 0x6EF45358; fingerprint:
E067 918B B660 DBD1 105C 966C 33F5 F005 6EF4 5358
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: not available
Url : http://lists.freedesktop.org/archives/dbus/attachments/20061114/a4463f12/attachment.pgp
More information about the dbus