#webassembly #wasm #wasmcloud #actor

wasmcloud-actor-core

wasmCloud Core Actor Interface

4 releases

new 0.2.3 Apr 16, 2021
0.2.2 Feb 22, 2021
0.2.1 Feb 16, 2021
0.2.0 Feb 10, 2021

#157 in WebAssembly

Download history 34/week @ 2021-02-04 429/week @ 2021-02-11 98/week @ 2021-02-18 168/week @ 2021-02-25 143/week @ 2021-03-04 150/week @ 2021-03-11 297/week @ 2021-03-18 133/week @ 2021-03-25 119/week @ 2021-04-01 171/week @ 2021-04-08 244/week @ 2021-04-15

610 downloads per month
Used in 24 crates (21 directly)

Apache-2.0

9KB
91 lines

crates.io  Rust license  documentation

wasmcloud Core Actor Interface

All actors must respond to the core HealthCheckRequest message with either an Err or a HealthCheckResponse. The following is an example of what an actor looks like that only responds to the health check message:

extern crate wasmcloud_actor_core as actor;
use wapc_guest::HandlerResult;
use actor::{HealthCheckRequest, HealthCheckResponse, Handlers};

 #[actor::init]
 fn init() {
     Handlers::register_health_request(health);
 }

 fn health(_msg: HealthCheckRequest) -> HandlerResult<HealthCheckResponse> {
     Ok(HealthCheckResponse::healthy())
 }

The actor::init macro defines a health check message responder that always returns healthy() by default. If you don't need to provide your own custom logic for the health check, then your init function can be simplified as follows:

extern crate wasmcloud_actor_core as actor;
use wapc_guest::HandlerResult;

#[actor::init]
fn init() {
    // register your message handlers here
}

Dependencies

~1.2–2MB
~45K SLoC