Add a ManagedEndpoint<PFooSide> type to allow for more complex actor construction
Categories
(Core :: IPC, enhancement, P2)
Tracking
()
Tracking | Status | |
---|---|---|
firefox68 | --- | fixed |
People
(Reporter: nika, Assigned: nika)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
This is specifically motivated by the desire to be able to allocate certain actors synchronously with their managers being connected. It is handled by passing around a type, like Endpoint<T>
, which is then used to bind the actors on either side.
No messages may be sent before the actors are constructed, or routing errors may occur.
Assignee | ||
Comment 1•6 years ago
|
||
Comment 2•6 years ago
|
||
How is this different from Endpoint? It has been a while since I looked at them.
Assignee | ||
Comment 3•6 years ago
|
||
Endpoint
is used to construct toplevel actors by establishing an underlying transport pipe which can be shared between the source & destination processes. These can then be linked to open a toplevel actor, and is how actors such as PBackground
are created.
In contrast, ManagedEndpoint
is intended to be used for constructing managed actors, which at the transport layer share the same pipe as the root actor, and route their messages to the correct destination based on the routing_id
attached to the message.
Updated•6 years ago
|
Comment 4•6 years ago
|
||
(In reply to :Nika Layzell from comment #3)
In contrast,
ManagedEndpoint
is intended to be used for constructing managed actors, which at the transport layer share the same pipe as the root actor, and route their messages to the correct destination based on therouting_id
attached to the message.
Thanks for the explanation! I've done a bit of work with Endpoints, but it was all for various GMP stuff, and I hadn't thought about how they were all top level actors.
Comment 6•6 years ago
|
||
bugherder |
Description
•