soledad.git/client/changes/feature_use-twisted-adbapi-for-sync-db, branch onepython [soledad] [pkg] fold in changes 2015-06-01T17:54:27+00:00 drebs drebs@leap.se 2015-06-01T17:54:27+00:00 9fb1c47ca7da06d6feef6846b812aec28128ed78 






[feature] use async adbapi for async decryption
2015-05-20T13:16:46+00:00

drebs
drebs@leap.se

2015-05-04T16:04:56+00:00

3a7ddacd06fd57afb10cc3d7083c2aa196c9328f

Since we started implementing twisted api in soledad, some pieces are missing.
Accessing the sqlcipher database directly with the twisted adbapi facilities
is one of them. The async encryption/decryption was touching the database
directly, and this was causing some difficulties like having different threads
accessing the same database. This commit implements the twisted adbapi stuff
for the asynchronous encryption/decryption facilities.

Next steps would be use async adbapi for async encryption and use async adbapi
for all sqlcipher access.





Since we started implementing twisted api in soledad, some pieces are missing.
Accessing the sqlcipher database directly with the twisted adbapi facilities
is one of them. The async encryption/decryption was touching the database
directly, and this was causing some difficulties like having different threads
accessing the same database. This commit implements the twisted adbapi stuff
for the asynchronous encryption/decryption facilities.

Next steps would be use async adbapi for async encryption and use async adbapi
for all sqlcipher access.