PendingCapture.
A capture the extension holds until the core accepts it: keyed like the capture, with its bytes, attempts and state
Figure 1PendingCapturespecified
- kind
- value
- scope
- none
- key
- none
- store
- none
- family
- sources
Fields#
| field | type | required | note |
|---|---|---|---|
key | hash | yes | the artefact’s hash with the person and the time |
scope | one of this item | this thread | this channel as shown | this page | this meeting | my outbound message | yes | |
under | one of say-so | rule | yes | |
rule | id | no | |
bytes | bytes | yes | |
attempts | count | yes | |
state | one of pending | sent | accepted | rejected | yes | the extension’s own state, never a place of the record |
reason | text | no |
Routes that use it#
No route takes or returns PendingCapture directly. The record holds it, and the objects that point at it reach it.