Re: [Evolution-hackers] API considerations for avoiding data loss in race conditions
- From: Matthew Barnes <mbarnes redhat com>
- To: hilberg kernelconcepts de
- Cc: evolution-hackers gnome org
- Subject: Re: [Evolution-hackers] API considerations for avoiding data loss in race conditions
- Date: Thu, 06 Dec 2012 10:43:40 -0500
On Thu, 2012-12-06 at 16:22 +0100, Christian Hilberg wrote:
> * EClient starts transaction / acquires lock on PIM
> entry
>
> * E-D-S records transaction start / gives away the PIM
> entry lock to the EClient requesting
>
> * EClient dies for any reason
>
> * Started transaction / aquired PIM lock persists in
> E-D-S
>
> What now? Timeout after some time? Welcome back to possible
> raciness (-->does not truly solve our problem).
This scenario is easily handled by watching the bus name of the client
process that acquired the lock. If the bus name vanishes, release the
lock immediately.
But we have no such transaction lock at present, do we?
Matt
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]