Expand description
Who is making a write, carried to the table’s lifecycle hooks.
A host (an API server handling a request, a desktop app acting for its
user) wraps the work in WriteContext::scope; every write awaited inside
it hands the context to its hooks through their context field. Vantage
doesn’t interpret it: principal is whatever record the host identifies the
actor with, and group ties together everything one request or action run
caused.
Structs§
- Request
Context - What the host saw of the request a write came in on. Built with
RequestContext::newand thewith_*builders.Debugshows cookie names only: their values are session credentials. - Write
Context - Built with
WriteContext::newand thewith_*builders, so a field added later (request data, say) doesn’t break existing hosts.
Enums§
- Transport
- The entry point a write came in through.
Constants§
- REQUEST_
HEADER_ ALLOW_ LIST - Headers a host may copy into a
RequestContext. Lowercase names. The host enforces it:RequestContext::with_headerstores whatever it is given.