| Age | Commit message (Collapse) | Author |
|---|
|
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.
|
|
size.
|
|
|
|
|
|
improve performance pretty decently under high load with lots of peers.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
ineffective.
|
|
location with pre-1.0.4 clients.
|
|
and replacing it with a simple non-crypto PRNG that just uses Salsa20.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
support code in Switch.
|
|
well supported or easily configurable anyway) -- this is really left over from the old collaborative multicast propagation algorithm. New algorithm (in for a while) has been sender-side replication in which sender "pays" all bandwidth, which intrinsically limits multicast.
|
|
full identity of peers instead of just address.
|
|
|
|
allow RENDEZVOUS from regular peers.
|
|
|
|
|
|
|
|
|
|
significantly simpler way to move all of this logic entirely into the containing service, liberating the core from any concern over the nature of its pipe to the outside world.
|
|
never work.
|
|
avoid flooding.
|
|
core, other bug fixes.
|
|
direct links.
|
|
|
|
|
|
|
|
link, porting over core loop code from old Node.cpp to new CAPI version, etc.
|
|
two-way handshake to prevent half-connects.
|
|
|
|
|
|
|
|
Switch.
|
|
|
|
simplifies a ton of stuff. Loads of spaghetti logic can die since we no longer have to make these decisions down in the core.
|
