f01c1e71b5
Begin work on sync...
2020-04-16 14:50:49 +02:00
2bea76ce16
Small refactorings
2020-04-12 22:24:53 +02:00
d1e8f78b2c
Trying to do TLS
2020-04-12 15:51:19 +02:00
5967c5a5af
Refactor a bit
2020-04-12 13:03:55 +02:00
9c931f5eda
Keep network status & ring in a tokio::sync::watch
...
advantages
- reads don't prevent preparing writes
- can be followed from other parts of the system by cloning the receiver
2020-04-11 23:53:32 +02:00
5dd59e437d
Local refcounting of blocks
2020-04-11 23:00:26 +02:00
dcf58499a4
table::insert_many, version_table::updated
2020-04-11 19:43:29 +02:00
53289b69e5
Background task runner that replaces tokio::spawn
2020-04-11 18:51:11 +02:00
cf8fd948fc
Add block ref table
2020-04-10 23:11:52 +02:00
3477864142
Fix the Sync issue. Details:
...
So the HTTP client future of Hyper is not Sync, thus the stream
that read blocks wasn't either. However Hyper's default Body type
requires a stream to be Sync for wrap_stream. Solution: reimplement
a custom HTTP body type.
2020-04-10 22:01:48 +02:00
d66c0d6833
Why is it not Sync??
2020-04-09 23:45:07 +02:00
1d786c2c66
Something works
2020-04-09 18:43:53 +02:00
101444abb3
Some progress
2020-04-09 17:32:28 +02:00
cc580da0ae
Some work
2020-04-08 23:01:49 +02:00
bacc76a057
Some work in actually storing things
2020-04-08 22:00:41 +02:00
d50edcdb4f
Basic workflow for client PUT, next is do actual storage
2020-04-08 00:39:07 +02:00
90cdffb425
custom data type for hashes and identifiers
2020-04-07 18:10:20 +02:00
82b7fcd280
Config management & ring
2020-04-07 17:00:48 +02:00
061e676136
Refactor; ability to update network config
2020-04-07 16:26:22 +02:00
