summaryrefslogtreecommitdiffstats
path: root/src/transport/mod.rs
Commit message (Collapse)AuthorAgeFilesLines
* put remake content into blobstv24 hours1-0/+6
|
* add chunked download and use it during rejointv26 hours1-0/+77
|
* add traffic countertv37 hours1-1/+26
| | | | | | | | | | This introduces a new wrapper that counts messages and payload bytes per peer, split by kind (hello, helloReply, sync, ping, pong), each sent, received and refused. The traffic counter goes around the firewall, which means messages dropped outbound are still counted as sent, and messages dropped inbound don't count as received.
* assess swarm stabilitytv37 hours1-0/+3
|
* use nonce in handshaketv39 hours1-0/+8
| | | | | To prevent stale hello replies to cause joins and thus stale sessions, each run gets a random ID, which used as nonce in the handshake.
* both sides may open sync after resettv44 hours1-0/+4
| | | | | | | | | | Ready nodes will leave the first message to the pear that isn't ready. Hello and hello reply now carry ready, so readiness is known from the very first contact, before any sync. Together with the sync messages and keepalives, reports_ready is always current. After epoch switch, pings go to everyone except ready members already on the new epoch, these learn from the lagging peer's opening.
* perform handshake in one round triptv44 hours1-0/+3
|
* bump number of heads in keepalive messagestv44 hours1-11/+38
| | | | | Instead of arbitrarily limiting the number to 16, allow filling keepalive messages as long as they don't cause mycelium to chunk it.
* enrich keepalive contenttv44 hours1-3/+46
| | | | | | | Add ready and syncs_with_you flags as well as actual heads, so the peer - ready: same meaning as in the sync message - syncs_with_you: sender counts recipient as member and in same epoch - heads: allows to tell who's behind or if both sides have changes
* use only ready peers as sync sourcetv45 hours1-0/+4
| | | | | | Sync messages now carries a ready flag, telling whether the sending peer itself is joined or is itself still (re-)joining. In the latter case, the peer won't be used as sync source.
* consistently use the words node, peer, and seedtv2 days1-2/+3
|
* introduce pre-shared swarm keytv3 days1-0/+4
|
* rename cluster to swarm everywhere!tv4 days1-2/+2
|
* reorganize all the modulestv5 days1-0/+98