diff options
author | Kali Kaneko <kali@leap.se> | 2013-12-19 21:52:12 -0400 |
---|---|---|
committer | Kali Kaneko <kali@leap.se> | 2013-12-19 22:08:26 -0400 |
commit | 7a6d913fed8fc8332174c7ac5c8a4a5472a478c3 (patch) | |
tree | ec31ec578b431111b81b077ae070578d2b795dca /client/changes/bug_reuse-http-connection | |
parent | cb616b80c47a5c251f4c66808396d0ac1352a390 (diff) |
Do not instantiate the synchronizer each time.
This has the nice effect of letting the persistent-connection
reuse the existing connection, avoiding the ssl handshake overhead
each time we try to synchronize.
This can be traced by logging the instantiation of HttpClientBase
in u1db.remote
I *think* we should be fine with the timeouts as long as we keep
the sync period along the 1 min we are doing now. For other cases,
we should look into how to override the default timeout in httplib
(used by u1db http_client).
Diffstat (limited to 'client/changes/bug_reuse-http-connection')
-rw-r--r-- | client/changes/bug_reuse-http-connection | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/client/changes/bug_reuse-http-connection b/client/changes/bug_reuse-http-connection new file mode 100644 index 00000000..c6cdd9b4 --- /dev/null +++ b/client/changes/bug_reuse-http-connection @@ -0,0 +1,2 @@ + o Fix a bug in soledad.client.sqlcipher by which we were creating + a new connection for each sync. |