https://github.com/wasmcloud/wascc-actor
Now deprecated in favor of using wapc-generated types and wrappers
https://github.com/wasmcloud/wascc-actor
actor-model actor-sdk rust rust-language wascc wasm webassembly webassembly-runtime
Last synced: 4 days ago
JSON representation
Now deprecated in favor of using wapc-generated types and wrappers
- Host: GitHub
- URL: https://github.com/wasmcloud/wascc-actor
- Owner: wasmCloud
- License: apache-2.0
- Archived: true
- Created: 2019-12-04T16:02:52.000Z (almost 6 years ago)
- Default Branch: master
- Last Pushed: 2020-12-03T13:24:37.000Z (almost 5 years ago)
- Last Synced: 2025-01-23T03:32:48.869Z (9 months ago)
- Topics: actor-model, actor-sdk, rust, rust-language, wascc, wasm, webassembly, webassembly-runtime
- Language: Rust
- Homepage: https://wascc.dev
- Size: 93.8 KB
- Stars: 33
- Watchers: 9
- Forks: 8
- Open Issues: 3
-
Metadata Files:
- Readme: README.md
- License: LICENSE.txt
Awesome Lists containing this project
README
[](https://crates.io/crates/wascc-actor)


[](https://docs.rs/wascc-actor)# DEPRECATED
This crate is no longer used as of 0.15.0. For actors targeting the 0.15.0 wasmCloud host, you will want to use waPC-generated types and wrappers that can be found in the [actor-interfaces](https://github.com/wascc/actor-interfaces) repository.# WebAssembly Secure Capabilities Connector - Actor SDK
The [waSCC Actor SDK](https://wascc.dev) 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](https://wascc.dev) website.
# Example
```rust
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.