status-go/geth/peers
Igor Mandrigin f4cd8d27b5 Add `shhext_getNewFilterMessages` function to RPC APIs.
This function returns only the new messages from the filter, never
returns the same message for the same user twice.
2018-04-27 15:24:37 +02:00
..
README.md Add signals for notifying react about discovery activity (#859) 2018-04-25 10:13:59 +03:00
cache.go Add `shhext_getNewFilterMessages` function to RPC APIs. 2018-04-27 15:24:37 +02:00
cache_test.go Add `shhext_getNewFilterMessages` function to RPC APIs. 2018-04-27 15:24:37 +02:00
discv5.go Peerpool failover (#801) 2018-04-12 16:08:49 +03:00
peerpool.go Add signals for notifying react about discovery activity (#859) 2018-04-25 10:13:59 +03:00
peerpool_test.go Add signals for notifying react about discovery activity (#859) 2018-04-25 10:13:59 +03:00
signal.go Add signals for notifying react about discovery activity (#859) 2018-04-25 10:13:59 +03:00
topic_peer_queue.go Add a priority queue to TopicPool (#840) 2018-04-19 17:18:49 +02:00
topic_peer_queue_test.go Add a priority queue to TopicPool (#840) 2018-04-19 17:18:49 +02:00
topic_register.go Peer pool to manage v5 peers (#736) 2018-04-10 09:44:09 +03:00
topicpool.go Make Limits type a struct 2018-04-21 00:03:40 +02:00
topicpool_test.go Make Limits type a struct 2018-04-21 00:03:40 +02:00

README.md

Peer pool signals

Peer pool sends 3 types of signals.

Discovery started signal will be sent once discovery server is started. And every time node will have to re-start discovery server because peer number dropped too low.

{
  "type": "discovery.started",
  "event": null
}

Discovery stopped signal will be sent once discovery found max limit of peers for every registered topic.

{
  "type": "discovery.stopped",
  "event": null
}

Discovery summary signal will be sent every time new peer is added or removed from a cluster. It will contain a map with capability as a key and total numbers of peers with that capability as a value.

{
  "type": "discovery.summary",
  "event": {
    "shh/6": 1
  }
}

Or if we don't have any peers:

{
  "type": "discovery.summary",
  "event": {}
}