Skip to main content

Module transaction_ids

Module transaction_ids 

Source
Expand description

Durable transaction-response deduplication.

Opaque response bytes are keyed by user, optional device, and transaction identifier. Room operations add a domain tag, the room, and a scope (the event type of a send, the target of a redaction) so independent scopes cannot replay one another’s responses.

Re-exportsΒ§

use std::sync::Arc; πŸ”’
use ruma::DeviceId; πŸ”’
use ruma::EventId; πŸ”’
use ruma::RoomId; πŸ”’
use ruma::TransactionId; πŸ”’
use ruma::UserId; πŸ”’
use tuwunel_core::Result; πŸ”’
use tuwunel_core::implement; πŸ”’
use tuwunel_database::Handle; πŸ”’
use tuwunel_database::Map; πŸ”’
use tuwunel_database::Txn; πŸ”’

StructsΒ§

Data πŸ”’
RoomTxn
A client transaction against one room.
Service
Persistent transaction-response lookup service.

EnumsΒ§

RoomScope
What a room transaction acts on within its room.

ConstantsΒ§

ROOM_DELAYED_TAG πŸ”’
ROOM_REDACT_TAG πŸ”’
ROOM_SEND_TAG πŸ”’

FunctionsΒ§

room_txnid_key πŸ”’
txnid_key πŸ”’

Type AliasesΒ§

Key πŸ”’
RoomKey πŸ”’