tiny.content.Sink

1/// Write capability over one provider, for a holder that may add bytes to a2/// store and nothing else. The capability carries three things: an opaque3/// context pointer for the provider, the capacity the store was built with, and4/// a function table whose single entry publishes bytes. Publishing is its whole5/// surface, so holding a Sink grants no way to read, look up, list, or delete.6pub const Sink = struct {7    context: *anyopaque,8    capacity: model.Capacity,9    vtable: *const VTable,1011    pub const VTable: type = SinkVTable;1213    /// Makes bytes retrievable under the reference a caller derived from them14    /// by checking the bytes against the reference and then asking the provider15    /// to publish them. The call rejects a reference whose extent is above the16    /// object ceiling first, with `ContentExtentExceeded`, and verifies the17    /// bytes against the reference next, so a length or digest disagreement18    /// stops the call before the provider sees anything. The call returns the19    /// provider's publication answer, `created` for new bytes and `exists_same`20    /// for bytes already held under this reference.21    pub fn put(22        self: Sink,23        reference: model.Reference,24        bytes: []const u8,25    ) PublicationError!Publication {26        try self.capacity.validateReference(reference);27        try reference.verify(bytes);28        return self.vtable.put(self.context, reference, bytes);29    }30};

1pub const Sink = capability.Sink;