@@ -382,12 +382,12 @@ then informs the King of the new state. The King manages snapshots of the Arvo
382state and handles I/O with Unix, among other things. The Serf only ever talks to
382state and handles I/O with Unix, among other things. The Serf only ever talks to
383the King, while the King talks with both the Serf and Unix.
383the King, while the King talks with both the Serf and Unix.
385−### Ames
385+### Ames I/O submodule
387The King has several submodules, one of them being an Ames I/O submodule. This
387The King has several submodules, one of them being an Ames I/O submodule. This
388submodule is responsible for wrapping outgoing Ames packets as UDP packets, and
388submodule is responsible for wrapping outgoing Ames packets as UDP packets, and
389−looking at incoming UDP packets handed to it by Unix to ensure that they are
389+unwrapping incoming UDP packets into Ames packets and forwarding them to the
390−valid Ames packets. It also maintains an incoming and outgoing packet queue.
390+worker. It also maintains an incoming packet queue.
392This division is summarized in the following diagram, describing how
392This division is summarized in the following diagram, describing how
393`~bacbel-tagfeb` requests a subscription to the `recipes` notebook of
393`~bacbel-tagfeb` requests a subscription to the `recipes` notebook of
@@ -403,12 +403,9 @@ Unix a `%send` `gift` containing that packet. This will be a Nock noun
403containing the `@tas` `%send` as well as the serialized packet.
403containing the `@tas` `%send` as well as the serialized packet.
405"Unix", in this case, is actually the King. The King receives the `%send`
405"Unix", in this case, is actually the King. The King receives the `%send`
406−instruction, wraps the packet contained within as a UDP packet, and queues the
406+instruction, wraps the packet contained within as a UDP packet, and immediately
407−UDP packet contained. Once it is time to send it (which will be determined by
407+hands it off the the Unix network interface to be sent.
408−congestion control), it will go ahead and forward the packet to Unix's
409−networking interface, at which point it is no longer controlled by any part of Urbit.
411Now the receiving King is handed a UDP packet by Unix. The King removes the UDP
409Now the receiving King is handed a UDP packet by Unix. The King removes the UDP
412−wrapped and checks to see that it has received a valid Ames packet. If so, it
410+wrapper, `+jam`s the `lane` on which it heard the packet, and delivers the packet
413−`+cue`s the payload and wraps it as a `%hear` `note` and passes it to the Serf.
411+to the Ames vane as an atom by copying the bytes it heard on the UDP port.