zephyr
af65c66317
vendor dependencies
2025-03-15 20:42:37 -04:00
zephyr
dd693fb000
less verbose logging
2025-03-15 20:41:14 -04:00
zephyr
773015dd15
add dockerfile
2025-03-15 20:38:49 -04:00
zephyr
94580d73be
implement data storage cli commands
2025-03-15 20:30:05 -04:00
zephyr
bfc9fe5d56
initialize node data maps
2025-03-15 20:29:47 -04:00
zephyr
4a69e64654
fix id parsing
2025-03-15 08:05:00 -04:00
zephyr
5d5155d8d8
implement lookup
2025-03-15 07:56:31 -04:00
zephyr
c0afd85f11
quit on leave
2025-03-14 23:10:49 -04:00
zephyr
bd2085ee87
implement leave command
2025-03-14 23:09:08 -04:00
zephyr
73068a9c1f
close the server when leaving
2025-03-14 22:50:50 -04:00
zephyr
ca35fd19db
implement graceful leaving
2025-03-14 22:43:44 -04:00
zephyr
2460f745bc
keys are owned by successor
...
Despite being certain I was doing it wrong, the behavior I had
implemented was to assign ownership of a key to the peer that knows the
key's successor, not to the successor of the key.
2025-03-14 15:49:41 -04:00
zephyr
b034852b34
add testing script
2025-03-14 12:32:34 -04:00
zephyr
afd8755131
log neighbors when stabilizing
2025-03-14 12:22:23 -04:00
zephyr
6316576823
check predecessor before stabilizing
2025-03-14 10:01:00 -04:00
zephyr
4c79714fcd
handle unexpected successor exit
2025-03-14 09:39:57 -04:00
zephyr
56c1ad3737
log find requests
2025-03-13 22:54:42 -04:00
zephyr
ecea53685f
actually return response value
2025-03-13 22:54:16 -04:00
zephyr
62c9693788
fix shadowed error
2025-03-13 22:33:04 -04:00
zephyr
730bb45db4
fix path parameter in notify
2025-03-13 22:15:25 -04:00
zephyr
8e73402c58
wrap stabilization errors
2025-03-13 22:10:28 -04:00
zephyr
7a04a22f76
run stabilization
2025-03-13 22:07:12 -04:00
zephyr
1e77429a91
join command implementation with create only
2025-03-13 21:57:33 -04:00
zephyr
9610513384
implement set on client/server
2025-03-13 21:20:26 -04:00
zephyr
4b44ffcd13
use path values instead of query parameters for lookup
2025-03-13 21:07:10 -04:00
zephyr
8047f4f13e
fix Find client url
2025-03-13 21:05:02 -04:00
zephyr
70f4e149d4
add Set operation
2025-03-13 20:58:14 -04:00
zephyr
ef03e13a87
don't handle keys that aren't owned
2025-03-13 20:54:31 -04:00
zephyr
f4a8b104ab
transmit value for key in find
2025-03-12 16:17:25 -04:00
zephyr
d5f26bb2bf
export key -> id conversion
2025-03-12 14:50:31 -04:00
zephyr
9c49d89637
move k/v store to nodes
...
Forgot that nodes have to own their data to implement leaving.
2025-03-12 14:49:20 -04:00
zephyr
ad0015a2be
add k/v store
2025-03-12 12:39:10 -04:00
zephyr
d9b1b5349a
synchronize Node methods
2025-03-12 12:13:41 -04:00
zephyr
936decf0e6
implement periodic checks in a function
2025-03-12 09:54:59 -04:00
zephyr
85e381f4bd
implement client neighbors
2025-03-11 09:58:20 -04:00
zephyr
68ce8c5f34
don't transmit nil predecessors
2025-03-11 09:27:45 -04:00
zephyr
93771480ff
implement client notify
2025-03-11 09:23:51 -04:00
zephyr
54d9536692
finish node server
2025-03-11 09:15:18 -04:00
zephyr
462a9783e9
start work on node server
2025-03-11 08:52:20 -04:00
zephyr
ae5f39fb34
implement more primitives
2025-03-11 08:51:46 -04:00
zephyr
ce8d109039
start FindSuccessor query
2025-03-09 23:50:32 -04:00
zephyr
45efc85a6e
implement node communications (Figure 6)
2025-03-09 12:45:57 -04:00
zephyr
7dd2de5055
add closest-preceding-node operation
2025-03-08 13:20:23 -05:00
zephyr
aa46693f58
add topology types
2025-03-07 18:06:03 -05:00
zephyr
ac31109615
add id representation
2025-03-07 16:09:48 -05:00
zephyr
2c650804fd
initial commit
2025-03-06 10:14:58 -05:00
zephyr