| Age | Commit message (Collapse) | Author |
|---|
|
initiated handoff. This might be the cause of the warmup problem -- will test later. At the very least it should not hurt anything due to pick-latest logic and the fact that cluster members with only suboptimal paths do not respond to WANT_PEER.
|
|
startup times, and add a result crunching script to tests/http.
|
|
|
|
peer if all we have is one of these. Also a few other small fixes.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
clusters to talk to each other, whereas forgetting all paths does not.
|
|
peer affinity tracking.
|
|
|
|
|
|
|
|
rate limiting in PUSH_DIRECT_PATHS for now (but we will do something else to mitigate amplification attacks)
|
|
|
|
Cluster function that checks for redirect, and clean up Peer::received() to be a bit more logical.
|
|
|
|
of certain frame types to avoid potential race conditions.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
warning, and fix a potential source of network recursion (though harmless).
|
|
serialize/deserialize into the class.
|
|
|
|
|
|
|
|
composition in one place.
|
|
tightening up multicast lookup and other things.
|
|
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.
|
|
controllers (for future use).
|
|
an active bridge.
|
|
|
|
helping. :(
|
