skip to content
[readonly]

7 packages match "tcp"

  • total 8
  • drwxr-xr-x-../
  • drwxr-xr-x-Oct 27 04:09@ajax/mesh-peer-link/# 0.1.0 The fleet's TCP links: bounded connects, the JOIN handshake both ways, the acceptor and dialers, a framed reader that refuses hostile lengths, and a writer that puts control frames before bulk ones
  • drwxr-xr-x-Oct 27 04:12@ajax/mesh-top-mock/# 0.1.0 A tiny mock of meshd's control port for mesh-top's tests and demo: synthesised snapshots, trace and log, a fake catalog, and a threaded TCP server
  • drwxr-xr-x-Oct 27 04:12@ajax/mesh-top-client/# 0.1.0 mesh-top's endpoint threads: one persistent meshd control-port connection each, polling snap and running the viewer's commands, with backoff and per-command reply timeouts
  • drwxr-xr-x-Oct 27 05:23@ajax/mesh-control/# 0.1.0 meshd's control port: one request line, one reply (a line or a framed body), every request byte for byte as the Rust
  • drwxr-xr-x-Oct 27 05:23@ajax/mesh-infer-wire/# 0.1.0 The gpt2 service protocol's wire: frames, key=value messages, checksummed KV layers
  • drwxr-xr-x-Oct 27 05:23@ajax/mesh-http-relay/# 0.1.0 meshd's HTTP port: request heads relayed to the GPU http program, and the routes meshd answers itself (the views, infer, render)
  • drwxr-xr-x-Oct 27 04:09@ajax/mesh-peer-relay/# 0.1.0 The fleet thread: links, the election and commit core, changes forwarded to the leader, the leader's policies and scheduler, migrations, lockstep groups and the published fleet state