mirror of
https://github.com/ilyakooo0/urbit.git
synced 2024-12-23 23:12:04 +03:00
6cbb6b060d
This reverts commit 8e1e40d75b3ab15c194b6bf9570f3edc46e2de58. This reverts commit f073c490f9fd7c5abc033af4857df92229877de7. This reverts commit f187d2d7e01a54823f3e979af9bbd148b398e7e9. This reverts commit bc272862a73cfce1b118586ca39d3a377d841f1b. This reverts commit 30a397513f8890a3406dc7ab91c6e067e3bbfbbb. This reverts commit 4fc6856fb50d88c20a0f533392ca606641c5f38f. Conflicts: urb/urbit.pill urb/zod/base/lib/drum.hoon
30 lines
1.1 KiB
Markdown
30 lines
1.1 KiB
Markdown
<div class="short">
|
|
|
|
`%ames`
|
|
=======
|
|
|
|
Our networking protocol.
|
|
|
|
`%ames` is the name of both our network and the vane that communicates
|
|
over it. When Unix receives a packet over the correct UDP port, it pipes
|
|
it straight into `%ames` for handling. Also, all packets sent over the
|
|
`%ames` network are sent by the `%ames` vane. Apps and vanes may use
|
|
`%ames` to directly send messages to other ships. In general, apps use
|
|
gall and clay to communicate with other ships rather than using `%ames`
|
|
directly, but this isn't a requirement. Of course, gall and clay use
|
|
`%ames` behind the scenes to communicate across the network. These are
|
|
the only two vanes that use `%ames`.
|
|
|
|
`%ames` includes several significant components. Although the actual
|
|
crypto algorithms are defined in zuse, they're used extensively in
|
|
`%ames` for encrypting and decrypting packets. Congestion control and
|
|
routing is handled entirely in `%ames`. Finally, the actual `%ames`
|
|
protocol itself, including how to route incoming packets to the correct
|
|
vane or app, is defined in `%ames`.
|
|
|
|
</div>
|
|
|
|
<hr>
|
|
</hr>
|
|
<list></list>
|