soledad.git/client/src, branch release/bitmask-0.9.x-alpha [soledad] [bug] fix a typo in the usage ISoledadPostSyncPlugin 2015-06-12T16:47:02+00:00 Ruben Pollan meskio@sindominio.net 2015-06-12T16:47:02+00:00 a70f2f0c74362b0b2d16b31b9b3ce66da9ce4b47 The variable was renamed in the definition but not where it's used. * Related: #7138 
The variable was renamed in the definition but not where it's used.

* Related: #7138
[style] minor style fixes for correction 2015-06-09T16:03:26+00:00 Kali Kaneko kali@leap.se 2015-06-09T16:03:26+00:00 6b0eab6ffa638fb521a524ce281212a796f12b04 after suggestions in the review 
after suggestions in the review
[refactor] use twisted logging facility to log failure 2015-06-09T15:40:03+00:00 Kali Kaneko kali@leap.se 2015-06-09T15:40:03+00:00 c097cfd5ef4fd0aef4ed91da3fcdae1e486f84f7 






[refactor] move collect_plugins to leap.common
2015-06-05T17:11:24+00:00

Kali Kaneko
kali@leap.se

2015-06-05T17:11:24+00:00

251155bf9228ac2f80ec6cf875e512e8b0ada0ac












[feature] filter documents before passing them to the plugin
2015-06-05T15:41:32+00:00

Kali Kaneko
kali@leap.se

2015-06-05T15:41:32+00:00

c849a67b986c826f128b045181d8b880744de104












[feature] use raw operation, returns no result
2015-06-05T15:22:42+00:00

Kali Kaneko
kali@leap.se

2015-06-04T14:23:50+00:00

6e3e31c0a357c633c0d52f996e4edd4bc159ccf7












[feature] add post-sync hooks using twisted plugins
2015-06-05T15:21:17+00:00

Kali Kaneko
kali@leap.se

2015-06-05T15:21:17+00:00

0093b9b7cf79b0e2e83cc76783152cc56c98f572

implementing a generic plugin interface to allow other modules to react
to soledad syncs, receiving a list of document ids that they've
subscribed to.

- Resolves: #6996
- Releases: 0.7.1





implementing a generic plugin interface to allow other modules to react
to soledad syncs, receiving a list of document ids that they've
subscribed to.

- Resolves: #6996
- Releases: 0.7.1







[bug] allow reuse of decr pool
2015-06-05T15:21:01+00:00

Kali Kaneko
kali@leap.se

2015-06-05T15:21:01+00:00

d3b7e95d11e25a321dd68bf4205049cb5a537ea9












[feature] increase the async encryption period
2015-06-03T19:07:50+00:00

drebs
drebs@leap.se

2015-06-02T11:42:24+00:00

289fab7dbeace040cdd6752026870e4d72e8265f

When async decrypting, we want to finish as fast as possible. When encrypting,
though, we don't have such a rush. With an encryption loop period of 2
seconds, we're able to encrypt 30 documents in one minute (the current bitmask
client sync period), which is meaningful: should moderatelly use the processor
while not syncing and relief from some work when actually syncing.





When async decrypting, we want to finish as fast as possible. When encrypting,
though, we don't have such a rush. With an encryption loop period of 2
seconds, we're able to encrypt 30 documents in one minute (the current bitmask
client sync period), which is meaningful: should moderatelly use the processor
while not syncing and relief from some work when actually syncing.







[bug] do not block when getting doc for async enc
2015-06-03T19:07:50+00:00

drebs
drebs@leap.se

2015-06-02T11:40:06+00:00

36d3fe05282bbc586c52536962cebf636a9b499f

Previous to this change, the actual encryption method used to run on its own
thread. When the close method was called from another thread, the queue could
be deleted after the encryption method loop had started, but before the queue
was checked for new items.

By removing that thread and moving the encryption loop to the reactor, that
race condition should disappear.

Closes: #7088.





Previous to this change, the actual encryption method used to run on its own
thread. When the close method was called from another thread, the queue could
be deleted after the encryption method loop had started, but before the queue
was checked for new items.

By removing that thread and moving the encryption loop to the reactor, that
race condition should disappear.

Closes: #7088.