mirror of
https://github.com/zap-proto/zip.git
synced 2026-10-19 15:38:57 +00:00
An op is an async fn. It may take &zip::Cx (request headers; the answer's status, headers and trailers) and a zip::Body read as it arrives, and may answer zip::Sse or zip::Body, each chunk written as the op yields it. A client that leaves drops the op's stream. The blocking std::net door is gone: HTTP/1.1 keep-alive and h2c on one port (hyper_util auto), graceful shutdown bounded by a grace. The ZAP door runs on tokio and streams with zap-proto/http's head, data and end frames. Wire names are serde's: the derive reads rename, rename_all, skip and with, and the hand-rolled JSON is deleted. The info manifest comes out byte for byte as before. No zapgen emits Rust, so the crate never built; the frame codec is written in zap.rs and pinned to frames Go wrote. The length prefix is big-endian, as zap-proto/http's transport writes it. examples/stream is a JSON op, an SSE op with a trailer and a byte relay, tested over raw HTTP/1.1, h2c and ZAP sockets. Claude-Session: https://claude.ai/code/session_01SCPMGSQsLNF2YtHFL4bwyp
52 lines
1.2 KiB
JSON
52 lines
1.2 KiB
JSON
[
|
|
{
|
|
"annotations": {},
|
|
"description": "Count streams n ticks as server-sent events, then [DONE], and reports how\nmany it sent in the x-sent trailer.",
|
|
"inputSchema": {
|
|
"properties": {
|
|
"everyMs": {
|
|
"description": "EveryMs is the pause before each tick, in milliseconds.",
|
|
"format": "uint64",
|
|
"type": "integer"
|
|
},
|
|
"n": {
|
|
"description": "N is how many ticks to send.",
|
|
"format": "uint32",
|
|
"type": "integer"
|
|
}
|
|
},
|
|
"required": [
|
|
"n"
|
|
],
|
|
"type": "object"
|
|
},
|
|
"name": "post_count"
|
|
},
|
|
{
|
|
"annotations": {},
|
|
"description": "Echo answers the text it was sent.",
|
|
"inputSchema": {
|
|
"properties": {
|
|
"text": {
|
|
"description": "Text is the line.",
|
|
"type": "string"
|
|
}
|
|
},
|
|
"required": [
|
|
"text"
|
|
],
|
|
"type": "object"
|
|
},
|
|
"name": "post_echo"
|
|
},
|
|
{
|
|
"annotations": {},
|
|
"description": "Relay answers the body it was sent, each chunk as it arrives, under the\ncontent type it was sent with.",
|
|
"inputSchema": {
|
|
"properties": {},
|
|
"type": "object"
|
|
},
|
|
"name": "post_relay"
|
|
}
|
|
]
|