Problem
When a user joins a graph, agents watching /updates on graph-store get an add-graph before there are necessarily any nodes (i.e. the backlog of the chat) in the graph. Since add-graph always has a blank graph when sent on /updates, and since add-graph with the 'backlog' of the chat prior to the user joining is not in update-log, there's no good timing solution (other than a thread checking recurrently, maybe?)
Proposed Solution
send an update on /updates when the initial 'backlog' is received by graph-store for a new graph.
Possible Alternatives
put the initial backlog in update-log scry
Problem When a user joins a graph, agents watching
/updates
ongraph-store
get anadd-graph
before there are necessarily any nodes (i.e. the backlog of the chat) in the graph. Sinceadd-graph
always has a blank graph when sent on/updates
, and sinceadd-graph
with the 'backlog' of the chat prior to the user joining is not inupdate-log
, there's no good timing solution (other than a thread checking recurrently, maybe?)Proposed Solution send an update on /updates when the initial 'backlog' is received by graph-store for a
new
graph.Possible Alternatives put the initial backlog in
update-log
scry