1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44

//! Info about connections to peer supernodes

use crate::peer::{Peer, PeerList, Peers};

pub struct PeersInfo {
    pub peers: Vec<PeerInfo>,
    pub announcements: usize,
    pub ann_by_hash_len: usize,
}

pub struct PeerInfo {
    pub addr: String,
    pub outstanding_requests: usize,
    pub msgs_on_wire: usize,
    pub msg_queue: usize,
}

impl Peers {
    pub fn get_info(&self) -> PeersInfo {
        let (hash_count, ann_count) = self.anns.lock().info();
        PeersInfo {
            peers: self.peers.info(),
            announcements: hash_count,
            ann_by_hash_len: ann_count,
        }
    }
}

impl PeerList {
    fn info(&self) -> Vec<PeerInfo> {
        self.list(|peer| peer.info())
    }
}

impl Peer {
    fn info(&self) -> PeerInfo {
        PeerInfo {
            addr: self.addr.clone(),
            outstanding_requests: self.get_outstanding_reqs_count(),
            msgs_on_wire: 0, //TODO No such concept in rust code - ask CJ what to do with it, remove or keep 0 for compatibility?
            msg_queue: 0,    //TODO originally "self.msg_queue.len()", not easy to get in Rust code - is it really needed, or can be dropped?
        }
    }
}