6ce14e2c9e
Make all requests continue in the background even after we got enough responses.
2020-04-16 23:13:15 +02:00
2bea76ce16
Small refactorings
2020-04-12 22:24:53 +02:00
9f8b3b5a18
TLS for command line client
2020-04-12 19:41:19 +02:00
419c70e506
fixes
...
- make block_put call uninterruptible by client
- used meta_replication_factor instead of data_replication_factor
- listen on ipv6
2020-04-12 12:10:33 +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
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
a50f07dfdc
Refactor
2020-04-10 22:26:48 +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
101444abb3
Some progress
2020-04-09 17:32:28 +02:00
4c1aee42d5
Reorganize table API
2020-04-09 16:16:27 +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
061e676136
Refactor; ability to update network config
2020-04-07 16:26:22 +02:00
