[doc] Describe different connection types
This commit is contained in:
1 parent
442abae2ba
commit
46578c03e9
1 file changed
+9
-6
@@ -113,13 +113,16 @@ struct CSerializedNetMsg
|
|||||||
std::string m_type;
|
std::string m_type;
|
||||||
};
|
};
|
||||||
|
|
||||||
|
/** Different types of connections to a peer. This enum encapsulates the
|
||||||
|
* information we have available at the time of opening or accepting the
|
||||||
|
* connection. Aside from INBOUND, all types are initiated by us. */
|
||||||
enum class ConnectionType {
|
enum class ConnectionType {
|
||||||
INBOUND,
|
INBOUND, /**< peer initiated connections */
|
||||||
OUTBOUND,
|
OUTBOUND, /**< full relay connections (blocks, addrs, txns) made automatically. Addresses selected from AddrMan. */
|
||||||
MANUAL,
|
MANUAL, /**< connections to addresses added via addnode or the connect command line argument */
|
||||||
FEELER,
|
FEELER, /**< short lived connections used to test address validity */
|
||||||
BLOCK_RELAY,
|
BLOCK_RELAY, /**< only relay blocks to these automatic outbound connections. Addresses selected from AddrMan. */
|
||||||
ADDR_FETCH,
|
ADDR_FETCH, /**< short lived connections used to solicit addrs when starting the node without a populated AddrMan */
|
||||||
};
|
};
|
||||||
|
|
||||||
class NetEventsInterface;
|
class NetEventsInterface;
|
||||||
|
|||||||
Reference in new issue
Block a user