Skip to main content

apply_writes

didbot_serve::routes::repo

Function apply_writes 

Source 
pub(crate) async fn apply_writes(
    __arg0: State<AppState>,
    headers: HeaderMap,
    __arg2: XrpcBody,
) -> Response
Expand description

POST /xrpc/com.atproto.repo.applyWrites

One commit, over every operation in the batch, so at most crate::wire::MAX_APPLY_WRITES of them. Every write is checked — against its collection’s lexicon, its record key strategy and the atproto data model — before any of them touches the store, so a batch that was going to be refused is refused whole rather than applied as a prefix; see didbot_pds::Registry::apply_writes. swapCommit is a genuine compare-and-swap against the commit this batch is about to replace, not a look before it: it is checked under the same lock the batch’s one commit is built under.