Module lib3h_zombie_actor::prelude

Re-exports

pub use super::WorkWasDone;

Structs

GhostContextEndpoint	an expanded endpoint usable to send/receive requests/responses/events see GhostEndpoint::as_context_endpoint_builder for additional details
GhostEndpoint	create_ghost_channel outputs two endpoints, a parent_endpoint, and a child_endpoint these raw endpoints are not very useful on their own. When you get them to the place they will be used, you probably want to call as_context_endpoint_builder() on them.
GhostError	GhostError used in GhostResult responses
GhostMessage	GhostContextEndpoints allow you to drain these incoming GhostMessages A GhostMessage contains the incoming request, as well as a hook to allow a response to automatically be returned.
GhostMutex
GhostMutexGuard
GhostParentWrapper	helper struct that merges (on the parent side) the actual child GhostActor instance, with the child's ghost channel endpoint. You only have to call process() on this one struct, and it provides all the request / drain_messages etc functions from GhostEndpoint.
GhostParentWrapperDyn	same as above, but takes a trait object child
GhostTrackRequestOptions
GhostTracker	GhostTracker registers callbacks associated with request_ids that can be triggered later when a response comes back indicating that id
GhostTrackerBookmarkOptions

Enums

ErrorKind	The specific type of an error.
GhostCallbackData	a ghost request callback can be invoked with a response that was injected into the system through the handle pathway, or to indicate a failure such as a timeout

Traits

GhostActor
GhostCanTrack	indicates this type is able to make callback requests && respond to requests

Functions

create_ghost_channel

We want to create a two-way communication channel between a GhostActor and its parent. create_ghost_channel will output two GhostEndpoint structures, the first one is the parent side, the second is the child's.

Type Definitions

GhostCallback	definition for a ghost request callback note, the callback can be registered as 'static because the code definition itself doesn't depend on any specific instance lifetime if you want to mutate the state of a struct instance, pass it in with the handle or process call. (see detach crate for help with self refs)
GhostResult	Result type for GhostErrors