on master help sign in
gall-guide: types - fix cage explanation
commit8d1fa0d865f3b6b2107f5cb05ed1b634f4c4e173 authorTinnus Napbus <admin@tinnus-napbus.xyz> dateTue 7 Dec 2021, 02:17 (5 years ago) parent9932785
1 file changed+3−7
content/docs/userspace/gall-guide/types.md+3−7
content/docs/userspace/gall-guide/types.md+3−7
@@ -124,13 +124,9 @@ documentation](/docs/arvo/clay/marks/marks).
124124A `cage` is a cell of a [`mark`](#mark) and a [`vase`](#vase), like `[%foo !>('bar')]`. The data in the vase should match the data type of the specified
125125mark.
126126
127−Most data sent between agents, either locally or over the network, will be in a
128−cage. When data comes in, Gall will validate the data in the vase with the given
129−mark. Additionally, the data may be converted to a different mark if appropriate
130−conversion routines exist in the mark file. This is most commonly done when
131−talking to a web front-end via Eyre's channel system - outgoing data will be
132−automatically converted to a `%json` mark and incoming data will be converted
133−from `%json` to the mark your agent expects.
127+Most data an agent sends will be in a `cage`, and most data it receives will
128+arrive in a `cage`. The `mark` may be used to validate or convert the data in
129+the `vase`, depending on the context.
134130
135131## `quip`
136132