History

Fix examples and modify new_node

- Fix examples `chat.py` and `echo.py`
    - Use trio directly, instead of `trio-asyncio`
    - Remove redundant code
- Change entry API `new_node` to `new_host_trio`

2019-12-24 18:03:18 +08:00

__init__.py

…

addrbook_interface.py

…

id.py

fixes #197

2019-12-17 11:00:45 +01:00

peerdata_interface.py

Move keypair into PeerData

2019-11-26 12:27:59 +08:00

peerdata.py

Apply PR feedback and fix

2019-11-26 14:04:28 +08:00

peerinfo.py

Fix examples and modify new_node

2019-12-24 18:03:18 +08:00

peermetadata_interface.py

…

peerstore_interface.py

Fix lint

2019-11-26 12:35:50 +08:00

peerstore.py

Apply PR feedback:

2019-11-26 16:18:15 +08:00

README.md

…

README.md

PeerStore

The PeerStore contains a mapping of peer IDs to PeerData objects. Each PeerData object represents a peer, and each PeerData contains a collection of protocols, addresses, and a mapping of metadata. PeerStore implements the IPeerStore (peer protocols), IAddrBook (address book), and IPeerMetadata (peer metadata) interfaces, which allows the peer store to effectively function as a dictionary for peer ID to protocol, address, and metadata.

Note: PeerInfo represents a read-only summary of a PeerData object. Only the attributes assigned in PeerInfo are readable by references to PeerInfo objects.