Skip to main content

Module endpoints

Module endpoints 

Source
Expand description

The resources, as endpoints.

Only two of them hold state — the script (its head and versions) and a run — and they hold it through the host’s Backend. Everything else is composed: …:result and …:runs read …:compiled through the kernel and hand the program to the language’s evaluator as a sub-request; urn:script:eval saves a draft by sinking to the script like any other writer.

Structs§

Catalog
The catalog’s JSON face.
CatalogEntry
One row of the catalog.
LastRun
A catalog row’s latest run.
Prepared
The compiled form: everything a run needs, in one cacheable resource hung from the script’s thread. For Lisp the “compilation” is preparation — the evaluator offers no separate compile step to cache — so this is the program and the authority it runs under, bound to the version they came from. For SPARQL it adds what the parsed text says: its form, its parameters and the graphs it names (Analysis).
ScriptSpace
The script resources as a space: space’s bindings, plus each published SPARQL script and plan as its own …:result and …:runs entry, carrying its parameters.
SpaceConfig
What a host decides when it mounts scripts: where they live and the ceiling it allows each one. Built with SpaceConfig::new and handed to space.

Constants§

TRANSPORT_ARGUMENTS
The argument names a TRANSPORT owns, which a run never reads as a script’s parameters (ledger #1173).

Functions§

space
Bind every script resource.

Type Aliases§

ChangeHook
What a host runs when a script’s head changes through this crate: see SpaceConfig::on_change.