status-im
/
status-research
mirror of https://github.com/status-im/status-research.git
2
0
Fork 0
Code Issues Projects Releases Wiki Activity

Move client concerns

This commit is contained in:
Oskar Thoren 2019-01-11 00:06:51 -05:00
parent 38fc88e203
commit 9db4a91558
2 changed files with 41 additions and 47 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

41
data_sync/client.py Normal file
View File

@ -0,0 +1,41 @@
# Interpreting messages, etc
# TODO: Expand message to be a payload with message hash
# TODO: Encode group with message graph and immutable messages
# NOTE: does nothing right now
# Should build up message graph and display
# What does a message look like, roughly:
ex = {'payload': "hello_world",
'content-type': "text/plain",
'signed_sender': 'A-signed-pubkey',
'dependencies': ["foo_message_id"]}
# TODO: Move to client
# XXX: This confuses things somewhat, as this is
# client concerns
#acc = "\n"
#for _, msg in a.messages.items():
# acc += msg.payload.message.body + "\n"
## XXX: Where is the sender stored? in msg?
#print "A POV:", acc
#acc = "\n"
#for _, msg in b.messages.items():
# acc += msg.payload.message.body + "\n"
#print "B POV:", acc
## TODO: Encode things like client, group scope, etc
# client\_id = R(HASH\_LEN)
CLIENT_ID = "0xdeadbeef"
class TestClient():
def __init__(self):
self.client_id = "0xdeadbeef"
# NOTE: Client should decide policy, implict group
# a.share("B")
# b.share("A")

47
data_sync/sync.py
View File

@ -5,16 +5,6 @@ import random
import sync_pb2
import time
# TODO: Expand message to be a payload with message hash
# TODO: Encode group with message graph and immutable messages
# TODO: Introduce latency and unreliability
# TODO: Encode mobile node bursty behavior better
## TODO: Encode things like client, group scope, etc
# client\_id = R(HASH\_LEN)
CLIENT_ID = "0xdeadbeef"
# Each group belongs to a client.
# Hardcoded for now.
# group\_id = HASH("GROUP\_ID", client\_id, group\_descriptor)
@ -341,22 +331,6 @@ def run(steps=10):
b.print_sync_state()
c.print_sync_state()
# TODO: Move to client
# XXX: This confuses things somewhat, as this is
# client concerns
#acc = "\n"
#for _, msg in a.messages.items():
# acc += msg.payload.message.body + "\n"
## XXX: Where is the sender stored? in msg?
#print "A POV:", acc
#acc = "\n"
#for _, msg in b.messages.items():
# acc += msg.payload.message.body + "\n"
#print "B POV:", acc
## TODO: Sync modes, interactive (+bw -latency) and batch (v.v.)
# Need to encode logic for actions taken at given time,
@ -404,15 +378,6 @@ def run(steps=10):
# Then C can offer messages to B, e.g.
# How viz message graph?
# TODO: Move into separate client namespace
# What does a message look like, roughly:
# This is actually client specific!
ex = {'payload': "hello_world",
'content-type': "text/plain",
'signed_sender': 'A-signed-pubkey',
'dependencies': ["foo_message_id"]}
# XXX: How will C receive the message from A to B?
# TODO: Requires offering to B, e.g.
# Or B requesting it
@ -431,17 +396,5 @@ ex = {'payload': "hello_world",
# It could play nice and offer all messages it has to C, but if C has all
# There needs to be some way for C to go for it, unless A is going to over-offer with bloom filter or so
# Look into this a bit more, naive way is signal
#
# Also think unreliability isn't necessary same as being offline and online
# Once online it is reliable, so it is bursty - how best encode that?
# Ok let's stop for now
run(30)
# Scenario:
# A online / offline / onlie
# B vice versa
# Why is B sending ACK to A if it is offline? not true?