tea-actor-utility

Crates.iotea-actor-utility
lib.rstea-actor-utility
version0.1.0
sourcesrc
created_at2020-05-02 19:09:02.322104
updated_at2020-05-02 19:09:02.322104
descriptionWasCC Tool - Supporting Binary and Sorted Vector Key-Value Pair and Macros to Build Nats Message Actor Handler
homepage
repository
max_upload_size
id236729
size17,415
Kevin Zhang (kevingzhang)

documentation

README

Tea Project WaSCC Actor Utility Supporting Binary and Sorted Vector Key-Value Pair and Macros to Build Nats Message Actor Handler

The Tea Project(also called T-Rust, or TeaRust)

Tea Project (Trusted Execution & Attestation) is a Wasm runtime build on top of RoT(Root of Trust) from both trusted hardware environment and blockchain technologies. Developer, Host and Consumer do not have to trust any others to not only protecting privacy but also preventing cyber attacks. The execution environment under remoted attestation can be verified by blockchain consensys. Crypto economy is used as motivation that hosts are willing run trusted computing nodes. This platform can be used by CDN providers, IPFS Nodes or existing cloud providers to enhance existing infrastructure to be more secure and trustless.

Introduction blog post

Project repo. More and more repo will be exposed soon.

Yet to come project site ( not completed yet) http://www.t-rust.com/

Contact: kevin.zhang.canada_at_gmail_dot_com.

We are just started, all kinds of help are welcome!

Motivation

WaSCC Actors are supposed to be stateless. Global variable and any kind of storage across handler calls are not recommended (although technically doable). Host provided key-value pair is one of the handy storage shared across handler functions.

WaSCC provided Redis provider and a sample key-value pair provider. There are a few reasons I cannot use them:

  • Redis is over kill to me.
  • Existing key-value pair provider use String, I prefer to use Vec
  • Writing the code direct call from actor is kind of cumbersome. Need an additional actor utility layer in between.

There is one more important reason for this later: To use macro to make Nats message actor handler code clean.

The actor handler code will look like this

actor_handlers!{ 
  codec::messaging::OP_DELIVER_MESSAGE => handle_nats_message, 
  codec::core::OP_HEALTH_REQUEST => health 
}

actor_messaging_handlers!{
  ("http", _, "bootstrap", "sync_from_other_actor",..) => sync_from_other_actor,
  ("http", _, "api", "request_active_nodes",..) => request_active_nodes, 
  //code snipet...
}

Please note the "_" act as the "*" in the Nats subscription wildcard as well as the ".." act as ">" in Nats subject. Think about writing code to handle those * and > wildcard without the macro.

So I made this library to scrach on my own itch. It can probably help you as well.

Build

Make sure you also clone the tea-codec repo at the same level because it is one of the dependencies.

tea-codec = { path = "../tea-codec"}

Then

cargo build

For unit testing

cargo test

Comments are welcome! Happy coding!

Commit count: 0

cargo fmt