diff options
author | John Newbery <john@johnnewbery.com> | 2017-10-17 16:16:39 -0400 |
---|---|---|
committer | John Newbery <john@johnnewbery.com> | 2017-11-29 17:14:48 -0500 |
commit | 873beca6deda119077f53921f0d19c3ebfc7cc44 (patch) | |
tree | 426d8ecde39b8bf44612d5a9b4098d676a5c5917 /test/functional/README.md | |
parent | 9f2c2dba21855b8cb9b193b1819be73fa4a23a99 (diff) |
[tests] Rename NodeConn and NodeConnCB
NodeConn -> P2PConnection
NodeConnCB -> P2PInterface
Diffstat (limited to 'test/functional/README.md')
-rw-r--r-- | test/functional/README.md | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/test/functional/README.md b/test/functional/README.md index 2558bd017d..193ca947bc 100644 --- a/test/functional/README.md +++ b/test/functional/README.md @@ -63,12 +63,12 @@ wrappers for them, `msg_block`, `msg_tx`, etc). with the bitcoind(s) being tested (using python's asyncore package); the other implements the test logic. -- `NodeConn` is the class used to connect to a bitcoind. If you implement -a callback class that derives from `NodeConnCB` and pass that to the -`NodeConn` object, your code will receive the appropriate callbacks when -events of interest arrive. +- `P2PConnection` is the class used to connect to a bitcoind. `P2PInterface` +contains the higher level logic for processing P2P payloads and connecting to +the Bitcoin Core node application logic. For custom behaviour, subclass the +P2PInterface object and override the callback methods. -- Call `NetworkThread.start()` after all `NodeConn` objects are created to +- Call `NetworkThread.start()` after all `P2PInterface` objects are created to start the networking thread. (Continue with the test logic in your existing thread.) |