| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
There were cases in the code where time calculations and comparisons were overflowing and causing connection instability. This will keep time calculations within expected ranges.
|
|
|
|
|
|
and more simply.
|
|
|
|
then passed to handler functions resulting from a call.
|
|
|
|
|
|
unknown networks to prevent forensics.
|
|
|
|
since they will need them to push auth for multicast stuff, (2) added a bunch of rate limit circuit breakers for anti-DOS, (3) cleanup.
|
|
|
|
|
|
elegant way.
|
|
protocol cleanup.
|
|
|
|
really parallel anyway and we fixed the perf problem.
|
|
|
|
length queues and merge queues. This is both faster and saves memory.
|
|
|
|
|
|
|
|
|
|
|
|
interface a full sockaddr_storage instead of an int identifier, which turns out to be better for multi-homing and other uses.
|
|
remote addresses.
|
|
|
|
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.
|
|
|
|
link, porting over core loop code from old Node.cpp to new CAPI version, etc.
|
|
Switch.
|
|
|
|
remaining on the network.
|
|
|
|
|
|
toggled.
|
|
|
|
|
|
Network to remove redundant code and bug-proneness, more work on IncomingPacket...
|
|
|
|
|
|
|
|
little more consistent about using _ to denote private member variables.
|
|
|
|
|
