Signal-Android/app
Greyson Parrelli 5ed6407ea3
No longer use a lock for RecipientCache.getSelf()
First, the only lock we can use for the time being is the database lock,
because if we use some other lock we could deadlock.

That said, it seems like we could avoid using a lock at all. The purpose
of the lock was to eliminate double-lookups, but if we have to acquire
the database lock to check if we need to do the lookup, we've lost the
advantage of doing so at all.

We *could* just do a traditional check-lock-check pattern to get the
lock far less often, but given that we're likely going to acquire it
during startup, even a single access has the possibility of really
gumming up the works.
2021-03-08 09:48:28 -05:00
..
.tx
jni
proguard
sampledata
src No longer use a lock for RecipientCache.getSelf() 2021-03-08 09:48:28 -05:00
build.gradle Use a new serviceID for the re-deployed KBS setup in staging. 2021-03-05 14:11:50 -05:00
lint-baseline.xml
lint.xml
translations.gradle Add Taqbaylit language support. 2021-01-22 10:59:42 -04:00
witness-verifications.gradle Update to RingRTC v2.9.4 2021-03-02 11:09:55 -08:00