Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
|
|
|
|
interface a full sockaddr_storage instead of an int identifier, which turns out to be better for multi-homing and other uses.
|
|
|
|
|
|
|
|
remote addresses.
|
|
|
|
|
|
to fail to keep associations alive behind some NATs.
|
|
|
|
|
|
|
|
size.
|
|
|
|
|
|
improve performance pretty decently under high load with lots of peers.
|
|
|
|
|
|
|
|
|
|
(ongoing std::map-ectomy)
|
|
|
|
principle of least surprise.
|
|
std::map() overhead.
|
|
|
|
possibly elsewhere.
|
|
|
|
controllers (for future use).
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
an active bridge.
|
|
|
|
|
|
|
|
|
|
helping. :(
|
|
|
|
paths to assist with (some) NAT traversal. (trying this, may back out if not effective)
|
|
ineffective.
|
|
|
|
(2) Go back to timestamp as certificate revision number. This is simpler
and more robust than using the network revision number for this and
forcing network revision fast-forward, which could cause some peers
to fall off the horizon when you don't want them to.
|