Teensie tidy up on actor doc string
parent
e03bec5efc
commit
1102843087
|
@ -452,17 +452,18 @@ class Actor:
|
||||||
(swappable) network protocols.
|
(swappable) network protocols.
|
||||||
|
|
||||||
|
|
||||||
Each "actor" is ``trio.run()`` scheduled "runtime" composed of many
|
Each "actor" is ``trio.run()`` scheduled "runtime" composed of
|
||||||
concurrent tasks in a single thread. The "runtime" tasks conduct
|
many concurrent tasks in a single thread. The "runtime" tasks
|
||||||
a slew of low(er) level functions to make it possible for message
|
conduct a slew of low(er) level functions to make it possible
|
||||||
passing between actors as well as the ability to create new actors
|
for message passing between actors as well as the ability to
|
||||||
(aka new "runtimes" in new processes which are supervised via
|
create new actors (aka new "runtimes" in new processes which
|
||||||
a nursery construct). Each task which sends messages to a task in
|
are supervised via a nursery construct). Each task which sends
|
||||||
a "peer" (not necessarily a parent-child, depth hierarchy)) is able
|
messages to a task in a "peer" (not necessarily a parent-child,
|
||||||
to do so via an "address", which maps IPC connections across memory
|
depth hierarchy) is able to do so via an "address", which maps
|
||||||
boundaries, and task request id which allows for per-actor
|
IPC connections across memory boundaries, and a task request id
|
||||||
tasks to send and receive messages to specific peer-actor tasks with
|
which allows for per-actor tasks to send and receive messages
|
||||||
which there is an ongoing RPC/IPC dialog.
|
to specific peer-actor tasks with which there is an ongoing
|
||||||
|
RPC/IPC dialog.
|
||||||
|
|
||||||
'''
|
'''
|
||||||
# ugh, we need to get rid of this and replace with a "registry" sys
|
# ugh, we need to get rid of this and replace with a "registry" sys
|
||||||
|
|
Loading…
Reference in New Issue