Rename all crates, CLI commands, constants, type names, doc comments, and documentation from wraith to alknet. Includes wire-protocol changes: ALPN wraith-ssh -> alknet-ssh, reserved destination prefix wraith- -> alknet-, SSH auth username wraith -> alknet.
1.6 KiB
1.6 KiB
id, name, status, depends_on, scope, risk, impact, level
| id | name | status | depends_on | scope | risk | impact | level | |
|---|---|---|---|---|---|---|---|---|
| transport/tcp-transport | Implement TcpTransport and TcpAcceptor | pending |
|
narrow | low | component | implementation |
Description
Implement the simplest transport: plain TCP. TcpTransport connects via TcpStream::connect(addr) on the client side. TcpAcceptor accepts via TcpListener::accept() on the server side. This is the baseline transport that all others build upon conceptually.
Acceptance Criteria
crates/alknet-core/src/transport/tcp.rsexportsTcpTransportandTcpAcceptorTcpTransportholds aSocketAddrtarget addressTcpTransport::connect()callsTcpStream::connect(addr)and returns the streamTcpTransport::describe()returns e.g."tcp://1.2.3.4:22"TcpAcceptorholds aTcpListenerand accept addressTcpAcceptor::accept()callslistener.accept(), returns(stream, TransportInfo)withremote_addrset andTransportKind::TcpTcpAcceptorconstructor binds the listener:TcpAcceptor::bind(addr)async factory- Connection timeout handling (tokio default connect timeout is reasonable; document behavior)
- Unit tests: connect creates a stream, accept receives a connection, describe format
- Integration test: client connects to server via TCP, stream is duplex
References
- docs/architecture/transport.md — TcpTransport row in implementations table
- docs/architecture/overview.md — "TCP on port 22 for basic use"
Notes
To be filled by implementation agent
Summary
To be filled on completion