Tweak supervison-proto into line

Tyler Goodlet 2025-03-24 13:02:10 -04:00
parent aace10ccfb
commit 293f23eaac
1 changed files with 7 additions and 7 deletions

View File

@ -6,18 +6,18 @@
``tractor`` is a `structured concurrency`_ (SC), multi-processing_ runtime built on trio_.
Fundamentally, ``tractor`` provides parallelism via
``trio``-"*actors*": independent Python *processes* (currently
*non-shared-memory threads*) which schedule ``trio`` tasks that
maintain SC *end-to-end* inside a *distributed supervision tree*.
``trio``-"*actors*": independent Python **processes** (i.e.
*non-shared-memory threads*) which can schedule ``trio`` tasks whilst
maintaining *end-to-end SC* inside a *distributed supervision tree*.
Cross-process (and thus cross-host) SC is accomplished through the
combined use of our,
- "actor nurseries_" which provide for spawning multiple, and
possibly nested, Python process trees each running a ``trio``
scheduled runtime - a call to ``trio.run()``,
- an "SC-transitive supervision protocol" implemented as an
IPC-message-spec enforced around each RPC-dialog.
possibly nested, Python processes each running a ``trio`` scheduled
runtime - a call to ``trio.run()``,
- an "SC-transitive supervision protocol" enforced as an
IPC-message-spec encapsulating all RPC-dialogs.
We believe the system adheres to the `3 axioms`_ of an "`actor model`_"
but likely **does not** look like what **you** probably *think* an "actor