on master help sign in
fixes for henry
ecfde25Galen Wolfe-Pauly
docs/programming/system/network.md+15−10
@@ -1,9 +1,11 @@
1---
1---
2next: false
2next: false
3sort: 2
3sort: 2
4−title: Network Messages
4+title: Network messages
5---
5---
6
6
7+# Network messages
8+
7Now we've learned enough hoon to do more interesting things.
9Now we've learned enough hoon to do more interesting things.
8Let's get our planets to talk to each other.
10Let's get our planets to talk to each other.
9
11
@@ -45,11 +47,13 @@ with the following commands:
45>=
47>=
46```
48```
47
49
50+<blockquote class="blockquote">
48−> There is currently a bug where the `%argument` lines are
51+There is currently a bug where the `%argument` lines are
49−> printed *above* the line you entered, so your output may not
52+printed *above* the line you entered, so your output may not
50−> look exactly like this.
53+look exactly like this.
51−> `>=` means that a command was successfully received and
54+`>=` means that a command was successfully received and
52−> executed.
55+executed.
56+</blockquote>
53
57
54Most of the app code should be simple enough to guess its
58Most of the app code should be simple enough to guess its
55function. The important part of this code is the definition of
59function. The important part of this code is the definition of
@@ -227,7 +231,8 @@ with one element:
227```
231```
228[ost %poke /sending [to-urbit-address %pong] %atom 'howdy']
232[ost %poke /sending [to-urbit-address %pong] %atom 'howdy']
229```
233```
234+
230−###Moves
235+### Moves
231
236
232The general form of a move is
237The general form of a move is
233
238
@@ -243,7 +248,7 @@ information]`
243
248
244Let's walk through each of these elements step by step
249Let's walk through each of these elements step by step
245
250
246−####Bones ("cause")
251+#### Bones ("cause")
247
252
248If you look up `++bone` in `hoon.hoon`, you'll see that it's a
253If you look up `++bone` in `hoon.hoon`, you'll see that it's a
249number (`@ud`), and that it's an opaque reference to a duct.
254number (`@ud`), and that it's an opaque reference to a duct.
@@ -288,7 +293,7 @@ called is also the root cause for the network message we're
288trying to send. Thus, we say to send the network message along the given bone
293trying to send. Thus, we say to send the network message along the given bone
289`ost`.
294`ost`.
290
295
291−#####Wire ('tack on new layer to duct')
296+##### Wire ('tack on new layer to duct')
292
297
293Of course, we have to push a new layer onto our duct
298Of course, we have to push a new layer onto our duct
294before passing it along (or responding to it directly) anywhere This
299before passing it along (or responding to it directly) anywhere This
@@ -302,7 +307,7 @@ handler as an argument. Although it's not required, it's
302generally a good idea to make the wire human-readable for
307generally a good idea to make the wire human-readable for
303bug-handling purposes.
308bug-handling purposes.
304
309
305−#####Term (sys-call)
310+##### Term (sys-call)
306
311
307Looking back at the general form of a move, there is a
312Looking back at the general form of a move, there is a
308`term`--which is text composed lowercase ascii and `-`, and has
313`term`--which is text composed lowercase ascii and `-`, and has