@@ -389,7 +389,8 @@ is all the subscribers from our ship to the foreign `desk`.
389`regs` are `(map path rule)`, and so `per` is a `map` of read permissions by
389`regs` are `(map path rule)`, and so `per` is a `map` of read permissions by
390`path` and `pew` is a `map` of write permissions by `path`.
390`path` and `pew` is a `map` of write permissions by `path`.
392−#### `++rind`, request manager
393+#### `$rind`, foreign request manager
395 ++ rind :: request manager
396 ++ rind :: request manager
@@ -398,27 +399,32 @@ is all the subscribers from our ship to the foreign `desk`.
398 fod=(map duct ,@ud) :: current requests
399 fod=(map duct ,@ud) :: current requests
399 haw=(map mood (unit)) :: simple cache
400 haw=(map mood (unit)) :: simple cache
402++$ rind :: request manager
403+ $: nix=@ud :: request index
404+ bom=(map @ud update-state) :: outstanding
405+ fod=(map duct @ud) :: current requests
406+ haw=(map mood (unit cage)) :: simple cache
403−This is the request manager for a foreign desk.
410+This is the request manager for a foreign `desk`. When we send a request to a
411+foreign ship, we keep track of it in here.
405−`nix` is one more than the index of the most recent request. Thus, it is
413+`nix` is one more than the index of the most recent request. Thus, it is the
406−the next available request number.
414+next available request number.
408−`bom` is the set of outstanding requests. The keys of this map are some
416+`bom` is the set of outstanding requests. The keys of this `map` are some subset
409−subset of the numbers between 0 and one less than `nix`. The members of
417+of the numbers between 0 and one less than `nix`. The members of the `map` are
410−the map are exactly those requests that have not yet been fully
418+exactly those requests that have not yet been fully satisfied.
413−`fod` is the same set as `bom`, but from a different perspective. In
420+`fod` is the same set as `bom`, but from a different perspective. In particular,
414−particular, the values of `fod` are the same as the values of `bom`, and
421+the values of `fod` are the same as the keys of `bom`, and the `duct` of the
415−the `p` out of the values of `bom` are the same as the keys of `fod`.
422+values of `bom` are the same as the keys of `fod`. Thus, we can map `duct`s to
416−Thus, we can map ducts to their associated request number and `++rave:clay`,
423+their associated request number and `update-state`, and we can map request
417−and we can map numbers to their associated duct and `++rave:clay`.
424+numbers to their associated `duct`.
419−`haw` is a map from simple requests to their values. This acts as a
426+`haw` is a map from `%sing` requests to their values. This acts as a cache for
420−cache for requests that have already been made. Thus, the second request
427+requests that have already been filled.
421−for a particular `++mood:clay` is nearly instantaneous.
423#### `++rang:clay`, data store
429#### `++rang:clay`, data store