wascc-actor

Crates.iowascc-actor
lib.rswascc-actor
version0.7.4
sourcesrc
created_at2019-12-04 16:15:22.208853
updated_at2020-09-09 14:52:40.291754
descriptionSDK for developing WebAssembly Actor modules for hosting in waSCC
homepagehttps://wascc.dev
repository
max_upload_size
id186430
size53,663
Kevin Hoffman (autodidaddict)

documentation

https://docs.rs/wascc-actor

README

crates.io  Rust  license  documentation

WebAssembly Secure Capabilities Connector - Actor SDK

The waSCC Actor SDK is used by Rust developers building cloud-native workloads for the wasm32-unknown-unknown target. Using waSCC to host your WebAssembly module frees you from the burden of manually implementing traditional non-functional requirements and boilerplate that typically bogs down development time. waSCC lets you focus solely on writing the business logic in a portable, secure wasm module that can run anywhere there's a waSCC host.

For more documentation, tutorials, and examples, please check out the wascc website.

Example

extern crate wascc_actor as actor;

use actor::prelude::*;

actor_handlers!{ codec::http::OP_HANDLE_REQUEST => hello_world, 
                 codec::core::OP_HEALTH_REQUEST => health }

fn hello_world(_req: codec::http::Request) -> ReceiveResult {

    // Utilize capabilities here
    // ...
    
    Ok(vec![])
}

fn health(_req: codec::core::HealthRequest) -> ReceiveResult { 
    Ok(vec![])
}

Debug output vs. using the wascc:logging capability

If you want more functionality beyond the simple println call, then you can sign your modules with the wascc:logging capability and you'll be able to use the idiomatic Rust log macros like debug!, warn!, trace!, etc.

Commit count: 0

cargo fmt