tiny.acp.TransferLimits

1/// A caller caps what the client writes to the agent and what it keeps from the agent, because the2/// agent is another program and can send without end. The structure sets five caps: the size of3/// each outgoing message, the size of each incoming update, the number of updates, and the size and4/// chunk count of one prompt's reply. Every cap must be above zero, and `Client.init` returns5/// `error.InvalidLimits` otherwise. `Options.transfer_limits` takes it and has no default. The6/// reader's line limit in `Options.reader_limits` is separate and applies to every incoming line7/// first.8pub const TransferLimits = struct {9    /// The largest message the client writes to the agent, in bytes, counting the newline that ends10    /// it. The limit applies to every message the client writes: `initialize`, `session/new`,11    /// prompts, permission answers, error answers and `session/cancel`. A larger message fails the12    /// call with `error.RequestCapacityExceeded` and nothing is written.13    request_bytes: usize,14    /// The most reply text, in bytes, one prompt keeps. The chunk that would pass it stays out of15    /// the reply, and the client sends `session/cancel`. The result then holds an overflow, and its16    /// kind is `response_bytes`. The limit counts again from zero for each prompt.17    response_bytes: usize,18    /// The largest update message the client accepts, in bytes of the line after surrounding19    /// whitespace is trimmed. A larger update fails the call with `error.UpdateCapacityExceeded`20    /// before the observer sees it.21    update_bytes: usize,22    /// The most update messages one client accepts over its whole life. The update sequence starts23    /// at 1 and never resets, so the first update numbered above this cap fails the call with24    /// `error.UpdateCountCapacityExceeded`.25    update_count: u64,26    /// The most agent message chunks one prompt's reply keeps. The chunk past it stays out of the27    /// reply, and the client sends `session/cancel`. The result then holds an overflow, and its28    /// kind is `response_segments`.29    response_segment_count: usize,3031    fn valid(self: TransferLimits) bool {32        return self.request_bytes != 0 and self.response_bytes != 0 and33            self.update_bytes != 0 and self.update_count != 0 and34            self.response_segment_count != 0;35    }36};

1pub const TransferLimits = client.TransferLimits;