Open lucktu opened 3 years ago
I think there should be a news, ... psp;
psp to p2p
Actually, this message already is in the code (src/edge_utils.c:816
). It will only be output at higher verbosity level.
The question is if these messages will clutter the output. If we lift this type of message to TRACE_NORMAL
, it will highly depend on edge's communication pattern how often this message will appear. It will be always re-printed when edges re-appear after a while (no communication in between, purged, seeing it again). For scalability, edges do no keep track of peers / other edges forever and they forget about them after a while without communication. So, seeing them again causes another output.
I am open to change it but I would wait for a broader discussion to make sure we will have found a stable majority on this point.
p2p to psp
I am not so sure about this type of message and how to identify this case. Anyone?
I mean display the current state correctly, no change, no news.
And the version of supernode.
And the version of supernode.
And the version of supernode.
894
Thank you! actually, I was hoping it would be in the message below:
25/Oct/2021 09:15:33 [edge_utils.c:3774] adding supernode = n2n.lucktu.com:10090 ... ... 25/Oct/2021 09:15:33 [edge_utils.c:1132] successfully joined multicast group 224.0.0.68:1968 25/Oct/2021 09:15:33 [edge_utils.c:2730] [OK] edge <<< ================ >>> supernode
The version number is not transmitted in REGISTER_SUPER_ACK but in PONG message. Hence, it cannot be displayed with this message which occurs on the very first REGISTER_SUPER_ACK.
This is information without p2p
I think there should be a news, ... psp; When the state changes(p2p to psp, or psp to p2p), there should also be a new message.