You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I placed here more data than necessary for your question, but I guess, that most important in that data is these parts:
distinction between info about replying node (the me property) and its peers, in the peers property.
the seen property is like last time any message received by this_node_unique_name from other_unique_name.
But joining node more likely to be bombarded with lots of replies, hello messages like this.
Imagine nodes bob, alice, and mike. Here mary comes and broadcasts her handshake message. This means that eventually mary will get hello messages from all them, identical or not, it depends from situation, because bob and mike for example can know henry but not know julia known to alice who knows nothing about henry. Joining node, mary can include list of known nodes in her handshake message like peers field from example, but what if some node sorta popular and knows hundreds of other nodes? Should it broadcast all this large list?
May be spreading handshake to other peers and replying with own information in hello reply message is enough, and no need to spread whole lists across network.
hi,
you did a great job with this little bookcase, congratulations!
how can I make the nodes share their neighbors with each other so that the network grows automatically
I had the following this steps in mind:
I'm not sure how to start art code, can I ask you for a suggestion? are the above steps right?
The text was updated successfully, but these errors were encountered: