Expand description
JSON DTOs shared by the HTTP/JSON transport (server handlers and the
reqwest client). The gRPC transport carries the same gonzalo-core types
as JSON bytes, so both transports agree on serialization.
Structs§
- Delete
Body - Body of
DELETE /v1/records/{ns}/{col}/{id}. The key is addressed by the URL path; the body carries the OCC precondition and, optionally, a claimed deleter identity. - Purge
Body - Body of
POST /v1/purge/{ns}/{col}/{id}(gonzalo#203). The key is addressed by the URL path.expectedis required, because purge is always conditional on the current revision. The response is aDeleteOutcome. - PutBody
- Body of
PUT /v1/records/{ns}/{col}/{id}. - RawRecord
Body - Response of
GET /v1/raw/records/{ns}/{col}/{id}(gonzalo#203). Absence is200 {"record": null}, never404: a404from this route means the daemon predates replication reads, and the client must tell the two apart without guessing.PUTon the same path takes aPutBodyand answers aPutOutcome.
Enums§
- Delete
Outcome - Response of a DELETE: mirrors
gonzalo_core::DeleteResulton the wire. - PutOutcome
- Response of a PUT: mirrors
gonzalo_core::PutResulton the wire.