Fabio Erculiani 87fd48eafe [Rigo] introduce SharedLocker to avoid reentrancy of Entropy Resources Lock ...

There are two issues with Entropy Resources Lock when used in Rigo.
1. Reentrancy: this property is unwanted in Rigo due to the amount
   of time Entropy Resources Lock is acquired and released.
   It is always wanted to acquire once and release once.
2. Re-acquiring it is costly, this lock should be relased only when
   we are really forced to do so.

2012-03-20 07:58:13 +01:00

..

data

[Rigo] add bottomNotificationBox GtkVBox

2012-03-17 17:09:58 +01:00

rigo

[Rigo] move RigoAuthenticationController to separate module

2012-03-19 18:54:25 +01:00

RigoDaemon

[RigoDaemon] rename is_exclusive() to exclusive()

2012-03-19 21:32:26 +01:00

rigo_app.py

[Rigo] introduce SharedLocker to avoid reentrancy of Entropy Resources Lock

2012-03-20 07:58:13 +01:00

test_polkit.py

[Rigo/RigoDaemon] greatly simplify resource passing rendezvous

2012-03-18 07:57:57 +01:00